Forks, WA Tourism Data: What Independent Hosts Should Fix First

Thomas Garner
7 days ago
12 min read

Updated: 9 hours ago

Empty covered porch of a Forks cedar cabin, no people

A host in Forks who quotes Hoh Rain Forest's visitor traffic as evidence their listing is a good investment is quoting the wrong number, and it's an easy mistake to make in a town where the rainforest, not the rental market, is what everyone actually talks about.

The two figures need to be kept in separate columns. Visitor draw explains why someone points a car toward the Olympic Peninsula in the first place — the Hoh Rain Forest's moss-draped canopy, Ruby Beach's sea stacks, the Timber Museum downtown, Olympic National Park's sheer size. Host performance explains what actually lands in an owner's account at the end of the year, and in Forks that number is $35,529 in typical annual revenue across 345 active listings, based on AirROI's trailing twelve months from August 2025 through July 2026. The average night ran $232, occupancy sat at 44.8 percent, and revenue per available night worked out to $120 — up 1.0 percent year over year, with active supply moving 21.1 percent over the same period.

None of that comes from a trail count or a park visitation figure. It comes from actual booking behavior, and it belongs in a host's own reporting the way the rainforest belongs in the listing's photo gallery — related, but never substituted for one another. This is not legal advice.

Visitor Demand and Occupancy Are Not the Same Number

Hoh Rain Forest is one of the most recognizable draws on the entire Olympic Peninsula, and it is unambiguously a demand signal — it's a real reason a guest chooses Forks over a dozen other towns within driving distance of the coast. What it is not is a substitute for the market's actual occupancy figure, which sits at 44.8 percent for the year. The rainforest doesn't fill the calendar in January the way it fills a July weekend, and a host who assumes heavy summer foot traffic at the trailhead translates evenly across twelve months is going to be surprised by how quiet January actually runs.

The honest way to use a landmark like this in a listing is as the answer to 'why would I come here,' not as a stand-in for 'how full does this place actually run.' Photograph the rainforest if a guest can realistically walk it during their stay — that's useful, accurate marketing. Filing visitor traffic figures as if they were booking data is a different kind of error, and it's the one that leads a host to over-forecast a slow month based on a landmark's year-round popularity rather than the market's actual seasonal occupancy curve.

The number that should anchor a host's own planning is the $35,529 typical annual revenue figure across the 345-listing sample, not any measure of how many people hiked to the rainforest that same year. One is a host's actual outcome; the other is a reason a guest showed up in town at all, and the two should never appear on the same line of a pro forma.

Ruby Beach Explains the Trip, Not the Rate

Ruby Beach is landscape — sea stacks, driftwood, a tide-pool coastline that draws a specific kind of traveler, disproportionately from Seattle first and Portland second, based on where most Forks guests actually originate. It's exactly the kind of feature that belongs in a hero photo and in the first paragraph of a listing description, because it answers the guest's real question about what the trip will feel like.

What it doesn't do is set a nightly rate. The market's actual average night is $232, and that figure holds regardless of how photogenic Ruby Beach happens to be on any given week. Revenue per available night lands at $120, which is the number that should inform a host's pricing strategy — not a landscape feature that draws visitors to the region generally rather than to any specific listing's calendar.

The practical takeaway for a host writing listing copy: keep the beach as the reason a Seattle-origin traveler pointed the car this direction, and keep $232 and $120 as the two numbers that actually describe what a night in this market is worth. Conflating the two doesn't make the listing more compelling — it just makes the host's own internal math less accurate.

The Timber Museum and Olympic National Park Are Traffic, Not Pricing Evidence

Downtown foot traffic around the Forks Timber Museum, and the broader visitation numbers for Olympic National Park itself, tell a host something real about why people are in the area — but neither one assigns an ADR to a specific listing. A busy museum parking lot or a crowded park visitor center on a Saturday doesn't move the market's actual average nightly rate of $232 up or down; it's simply evidence that a lot of people are nearby that day, which is a different fact from how much any of them are willing to pay for a night's stay.

The same logic applies to picnic tables, trailheads, and any other physical feature a host might be tempted to describe as revenue-generating on its own. None of it is revenue per available night, which sits at $120 for this market regardless of how busy the park's most popular overlooks get on any given weekend. A host writing a listing guide for guests should photograph the stop a guest can actually finish during their stay — the museum, a specific park trail, a beach access point — and leave the pricing conversation to the market's own performance numbers.

This distinction matters most when a host is trying to justify a rate increase to themselves. 'The park had record visitation this summer' is not the same claim as 'occupancy or ADR moved in this market,' and treating the two as interchangeable is how a host ends up pricing a summer weekend against a headcount instead of against what guests in this specific market have actually been paying.

Keeping Visitor Dollars Off the Host's Own Extract

Tourism copy is genuinely useful for explaining why a guest came to Forks in the first place — it just doesn't belong anywhere near a host's own performance reporting. The number that does belong there is $35,529 in typical annual revenue across the 345-listing sample, with year-over-year growth of 1.0 percent and active supply movement of 21.1 percent over the same trailing-twelve-month window.

A host building their own year-end summary, or preparing a pro forma for a new property in this market, should treat visitor headcounts from the rainforest, the beach, the museum, or the park as color for the listing description and nothing more. The $35,529 figure, the $232 average night, the 44.8 percent occupancy, and the $120 revenue per available night are the actual inputs that belong in a spreadsheet — and the discipline to keep those two categories separate is, in practice, the single biggest difference between a host's pro forma that holds up and one that doesn't.

This is also where the market's supply story matters. Active listing supply moved 21.1 percent over the trailing twelve months, which is a meaningful shift in competitive density for a market of this size. A host modeling next year's occupancy should factor that supply movement in alongside the 44.8 percent baseline occupancy figure, rather than assuming last year's fill rate simply repeats on a static supply count.

Forks and Florence Are Two Different Files

Florence, a comparably sized coastal town, posts its own figures — a typical annual revenue of $28,974 across 212 active listings — and those numbers describe an entirely different market with its own calendar, its own guest origin mix, and its own supply dynamics. Blending Forks and Florence into a single performance claim, even informally in a listing description or an owner's own notes, misrepresents both markets at once.

The two towns do share a summer season in the broad sense that most Pacific Northwest coastal markets run their strongest months between late spring and early fall, but shared seasonality is not the same as an identical shoulder-season pattern. Forks' three strongest months are August, June, and September, with August the clear peak and January the clear low point in occupancy. A host in Forks who imports Florence's shoulder-season assumptions into their own pricing calendar is applying a stranger's seasonal curve to their own property.

Keeping Florence's $28,974 on 212 listings on its own line, and Forks' $35,529 on 345 listings on its own separate line, isn't pedantic — it's the difference between a pro forma that reflects the market a property actually sits in and one that quietly borrows numbers from a town ninety minutes and one state away.

Booking Patterns and Host Composition Worth Knowing

Beyond the headline revenue figure, a few structural details describe how this specific market actually operates day to day. The typical stay length runs 2.6 nights, and guests book roughly 51 days ahead of arrival on average — both useful numbers for a host deciding how far out to open the calendar and how aggressively to adjust pricing as a specific date approaches without bookings yet in hand.

Superhost share in this market sits at 84.6 percent, and professionally managed listings make up 9.0 percent of the sample — a market composition that skews heavily toward experienced, independent operators rather than large management companies. That matters for a new host evaluating the competitive set: the properties competing for the same guest are disproportionately run by owners who have already earned Superhost status, not by a handful of dominant management brands, which changes what actually differentiates a listing here compared to a market where a few large operators control most of the listing stock.

None of these figures — stay length, booking window, Superhost share — are tourism statistics. They're host-side operating data drawn from the same market performance file as the revenue and occupancy numbers, and they belong in the same planning conversation, not in the same bucket as a trailhead visitor count.

Confirming What the City Actually Requires Before Listing

Forks City Desk sits at 500 East Division Street, open Monday through Friday from 8 to 5, and the city does not issue a separate city business license for short-term rentals. A dedicated 2026 STR permit fee was not confirmed as a live dollar amount on the primary city page as of this pass, which means a host should not repeat an unverified number as if it were settled policy — the responsible move is to confirm current zoning and any permit requirement directly with the city before listing a new property, rather than relying on a secondhand figure that may already be out of date.

The same caution applies to festival dates and other calendar-based claims: named 2026 festival dates were not locked from a primary calendar as of this pass, so a host writing seasonal marketing copy should lean on the confirmed seasonal pattern — August, June, and September as the three strongest months, January as the softest — rather than promising guests a specific festival date that hasn't been verified against the town's own primary source.

The throughline across all of this is the same one that runs through the tourism-versus-occupancy distinction above: file what's confirmed as confirmed, file what isn't as unconfirmed, and don't let a landmark's popularity or an assumed permit fee stand in for a number a host hasn't actually verified. That habit is worth more to a host's bottom line than any single piece of marketing copy about the rainforest.

A Worked Example: Building an Actual Pro Forma From These Numbers

Take a three-bedroom property considering entry into the Forks market. Using the market's typical annual revenue of $35,529 across 345 listings as the baseline, and the $232 average night against 44.8 percent occupancy, a new owner can build a rough first-year model without ever touching a visitor count. At $232 a night and 44.8 percent occupancy, that works out to roughly 163 booked nights across the year — a figure that lines up reasonably with the market's typical stay length of 2.6 nights and a booking cadence that peaks hard in August, June, and September and falls off sharply in January.

The mistake a new host is most likely to make at this stage is assuming the property will outperform the market average simply because Hoh Rain Forest or Ruby Beach had a strong tourism year. Visitor headcount at a national park entrance doesn't move a single line of this math — the $120 revenue per available night and the 44.8 percent occupancy baseline are the numbers that actually flow into a realistic first-year projection, and a new host should build their model off those figures, then treat any premium positioning around proximity to the rainforest or the beach as upside to test for, not a number to bake into the base case.

The 21.1 percent active-supply growth over the trailing twelve months is the other input worth stress-testing against. A market adding new listings at that pace can see occupancy compress for existing properties even if overall demand holds steady, simply because more listing stock is splitting the same booking pool. A conservative pro forma for a new Forks listing should model occupancy at or slightly below the 44.8 percent market baseline in year one, rather than assuming a new, well-photographed listing will immediately outperform an already-growing competitive set.

Frequently Asked Questions

Does heavy Hoh Rain Forest visitor traffic mean high occupancy in Forks?

No. Hoh Rain Forest drives sightseeing traffic, not bookings on its own. Occupancy sits at 44.8 percent for the year, and the rainforest's popularity doesn't fill the slow month of January the way it fills a summer weekend. Use it as a photo opportunity and a reason-to-visit in the listing, not as a rate justification.

How does Ruby Beach factor into a Forks STR listing?

Ruby Beach explains why a guest, especially one traveling from Seattle, points the car toward Forks in the first place — but it says nothing about revenue. The market's actual numbers are $35,529 in typical annual revenue across 345 active listings, a $232 average nightly rate, and $120 in revenue per available night.

What should hosts take from the Forks Timber Museum and downtown foot traffic?

Treat it as a stop a guest can realistically finish during a stay, not as pricing evidence. Museum or downtown foot traffic doesn't move the average nightly rate, which sits at $232 in this market independent of how busy the village gets on any given day.

Does Olympic National Park's visitation explain the Forks ADR?

No — park visitation is a traffic count, not a revenue metric. The market's actual revenue per available night is $120. Confirm park hours directly with the park before promising guests a specific hike or viewpoint will be open during their stay.

Why shouldn't hosts cite tourism headcounts as their own performance data?

Tourism copy explains motivation, not income. The performance figures that actually belong in a host's own reporting are $35,529 in typical annual revenue across the 345-listing sample, up 1.0 percent year over year, with active supply moving 21.1 percent over the same period. Those are the numbers a spreadsheet should reflect, not a trailhead visitor count.

Is Florence, Oregon's occupancy data relevant to a Forks listing?

No. Florence is a separate market with its own figures — about $28,974 in typical annual revenue across 212 active listings. Blending the two towns into a single performance claim misrepresents both markets, even though they share a broadly similar Pacific Northwest coastal season.

Do Forks and Florence share the same seasonal calendar?

They share a general summer season but not an identical shoulder-season pattern. In Forks specifically, August, June, and September are the three strongest months, with August the busiest and January the slowest. A host shouldn't borrow Florence's shoulder-season timing as a stand-in for Forks' own calendar.

What's the practical takeaway for a host writing tourism-related listing copy?

File Hoh Rain Forest, Ruby Beach, and similar draws under 'why guests come,' not 'what we earn.' Keep $35,529 as the actual performance number for the year, and confirm operating details like city hall hours or permit requirements directly with the city rather than assuming them from tourism materials.

What does the typical guest stay and booking window look like in Forks?

Typical stays run 2.6 nights, and guests book about 51 days ahead of arrival on average. That booking window gives a host a practical sense of how far in advance a specific date's pricing needs to be locked in versus left open for late demand.

What does the host composition in this market look like?

Superhost share sits at 84.6 percent, and professionally managed listings make up 9.0 percent of the sample — a market weighted toward experienced independent operators rather than dominated by a handful of large management companies.

Is there a confirmed short-term rental permit fee in Forks for 2026?

Not as a verified, live dollar figure on the city's primary page as of this pass. The city does not issue a separate city business license for STRs, and a host should confirm current zoning and any permit requirement directly with City Hall at 500 East Division Street rather than repeating an unconfirmed number.

How much has active STR supply changed in the Forks market recently?

Active supply moved 21.1 percent over the trailing twelve months measured from August 2025 through July 2026 — a meaningful shift in competitive density that a host should factor into next year's occupancy expectations rather than assuming last year's fill rate applies to an unchanged competitive set.

Work with Crest & Cove Creative

Forks, WA Tourism Data: What Independent Hosts Should Fix First only works when the listing shows operable facts guests can check. Cut soft slogans that hide the real stay.

Confirm zoning and any permit requirement directly with City Desk at 500 East Division Street before you list, and keep the rainforest in the photo gallery, not the pro forma. Reach out at crestcove.co or (256) 998-7502.

Reach out at crestcove.co or (256) 998-7502.