So here's what actually happened. Poland drafted legislation that reclassifies any rental under 30 days as a hotel service. That means roughly 65,000 short-term rental apartments... many of which have been operating with zero oversight, zero fire safety compliance, and zero tax accountability... now need to register with a national database called CWTON, get a unique ID number, and display that number on every listing. Platforms like Airbnb and Booking.com aren't just passive middlemen anymore. They're required to verify registration numbers and share monthly data with authorities. Fines for non-compliance hit up to PLN 50,000 (about €11,600). And here's the part that matters most for hotels: local municipalities can now designate zones where short-term rentals are restricted or banned entirely.

This isn't Poland inventing something new. It's Poland catching up to EU Regulation 2024/1028, which went into effect May 20, 2026. But Poland still hasn't finalized its national implementation legislation (the draft is called UC135, with a proposed transition deadline of October 1, 2026), which means right now there's a grey zone where nobody... operators, platforms, local authorities... knows exactly what's enforceable. The estimated grey market is 30-35% of the sector. That's roughly 20,000 apartments operating completely off the books. The question isn't whether regulation is coming. It's whether the enforcement infrastructure actually exists to make it mean something.

Look, I've been in technology evaluation meetings where someone presents a beautiful compliance dashboard and I ask "okay, but who's checking the data?" That's the fundamental issue with every STR registry I've seen proposed or implemented. The technology to build the database is trivial. I could build CWTON in a weekend (I'm not even exaggerating... it's a registration form, a unique ID generator, and an API for platforms to query). The hard part is enforcement. Who verifies that the apartment listed as "fire-safety compliant" actually has a working smoke detector? Who checks that the operator displaying registration number PL-47291 on their Airbnb listing is the same person who registered that number? Who follows up when a property gets three noise complaints and should be removed from the registry? If the answer is "local authorities," then you need to ask what local authorities' technology stack looks like and how many staff they have dedicated to this. In most European municipalities, that answer is "not enough."

The platform accountability piece is actually the most interesting part of this architecturally. Requiring Airbnb and Booking.com to verify registration numbers before allowing listings to go live... that's pushing compliance enforcement upstream to entities that actually have the technical infrastructure to do it. It's smart. But it only works if the platforms cooperate meaningfully, and their track record on that across Europe is mixed at best. Airbnb has historically preferred to negotiate city-by-city, delay implementation, and argue about data-sharing scope. Monthly data reporting to authorities is a significant operational change for platforms, and I'd want to see the actual API specification and data schema before I believed it was anything more than a PDF export someone runs manually.

For hotel operators competing against unregulated STRs... this is directionally good but operationally uncertain. The 30-35% grey market isn't going to disappear because a law passed. It'll shrink, maybe significantly, but enforcement determines the actual competitive impact. What I'd watch is whether municipalities actually use the zoning powers they're being given. That's the real lever. A registration requirement raises the cost of operating an STR. A zoning restriction removes supply from the market entirely. Those are very different outcomes for your comp set.

$7,355,000 for 32 units in Indian Harbour Beach, Florida. That's $229,844 per door with a stated NOI of $514,930 and a 7% cap rate on a property split evenly between 16 furnished short-term rental units and 16 long-term apartments. The structure is the story here. This isn't a traditional multifamily deal and it isn't a hotel. It's a hybrid that prices like residential and competes like lodging.

Let's decompose the 7% cap. On $514,930 NOI, the buyer is paying 14.3x earnings for an asset whose revenue upside depends entirely on the continued legality and demand for sub-90-day stays in Brevard County. Florida state law prevents municipalities from outright banning short-term rentals, but Brevard County enforces a 90-day minimum rental period in most residential zones. This property apparently sits in a permissible district. "Apparently" is doing a lot of work in that sentence. A buyer paying $7.35M needs to verify that zoning classification survives the next county commission meeting, because the regulatory trend line in Florida's coastal markets is tightening, not loosening.

The 50/50 split is what makes this interesting from an underwriting perspective. Sixteen long-term units provide base cash flow. Sixteen STR units provide the seasonal upside that gets the cap rate to 7%. Strip out the short-term units and model them at long-term rental rates... the cap rate compresses to somewhere in the low 5s (generous estimate). The premium the seller is capturing is the STR optionality. The risk the buyer is absorbing is whether that optionality survives regulatory change, platform algorithm shifts, and competitive saturation from every other Space Coast property owner who figured out the same Airbnb playbook.

For hotel owners and asset managers in the Brevard County comp set, this listing is a useful data point. A 32-unit hybrid operating at a stated 7% cap is pulling demand from the same leisure traveler pool that fills your select-service and extended-stay properties during launch weeks and cruise embarkations. The per-unit operating cost structure of an apartment complex (no front desk, no daily housekeeping labor, no brand fees, no loyalty program assessments) gives it a margin advantage that traditional hotels can't replicate without fundamentally changing what they are. That cost gap is the structural threat, not the unit count.

One number to watch: Brevard County's 5% Tourist Development Tax applies to stays under six months. That tax funds destination marketing that benefits hotels. Every STR unit paying into that fund is, in theory, contributing to the demand ecosystem. In practice, the incremental supply pressure from hybrid properties like this one erodes the rate ceiling for traditional hotels faster than the tax revenue compensates. An owner I spoke with last year in a similar Florida coastal market put it simply: "They're paying into my marketing fund while stealing my guests. The math doesn't net out in my favor."