Airbnb Multi-Listing Hosts by City
Pricing
from $18.00 / 1,000 host portfolios
Airbnb Multi-Listing Hosts by City
Find the hosts running more than one Airbnb listing in a city. One row per host with portfolio size, superhost status, average rating, total reviews and median price. The listing data is public; the portfolio is not, and that is the product.
Pricing
from $18.00 / 1,000 host portfolios
Rating
0.0
(0)
Developer
Carlos Escanez
Maintained by CommunityActor stats
0
Bookmarked
3
Total users
1
Monthly active users
7 hours ago
Last modified
Categories
Security
Limited permissionsShare
Airbnb Multi-Listing Hosts — who runs more than one flat in a city
Not a list of listings. A list of the operators behind them: one row per host with two or more listings in a city, sorted by portfolio size.
- The grouping is the product. The listings are public; who runs which of them is not, and that is what each row gives you.
- Every figure comes from the public listing pages: superhost status, rating, reviews, price, guest capacity. Nothing is estimated.
- $0.02 per host row. Raw listing rows, if you ask for them, are $0.002 each.
Try it now: the input comes filled with Austin, TX and 20 pages. Press Start: between one and two minutes and about $0.75 (37 hosts in each of two checks on 5 November 2026).
See it run
Airbnb shows you a listing at a time. It never shows you that seven of the flats you just scrolled past belong to the same person. This Actor works that out by comparing host ids across a whole city, and hands you one row per host:
7 listings | Marta | Superhost | 4.91 | 1,204 reviews | median $148 | 34 beds5 listings | Urban Stay | Superhost | 4.78 | 612 reviews | median $210 | 22 beds2 listings | Diego | | 4.96 | 29 reviews | median $119 | 8 beds
Sorted by portfolio size, because the operator with twenty flats is a business and the one with two is a hobby.
What you get per host
Portfolio size. Superhost status and how many of their listings hold it. Average rating across the portfolio, total reviews, median, minimum and maximum price. Total guest capacity. How many listings are Guest Favourites. A sample of their listings with names, links and prices. Their public profile link.
In listings mode you get the raw rows instead: name, price, rating, reviews, capacity, property type, coordinates, and the host id that ties them together.
Who buys this
- Property management companies — the whole pitch is "let us run your flats". A host with five listings is a qualified lead; a host with one is not.
- Dynamic pricing and channel manager tools — same reason, and portfolio size predicts willingness to pay for software.
- Cleaning, laundry and maintenance firms — one operator with twenty flats is worth twenty individual owners.
- City councils and housing researchers — concentration of short-term rentals in the hands of few operators is the exact number these studies need.
- Investors — where the professionals are already operating tells you the market works.
Example inputs
Professional operators only, two cities
{"locations": ["Lisbon, Portugal", "Porto, Portugal"],"minListings": 3,"pagesPerLocation": 20}
Everyone with a second flat, in euros
{"locations": ["Madrid, Spain"],"minListings": 2,"currency": "EUR"}
Raw listings for your own analysis
{"locations": ["Austin, TX"],"outputMode": "listings","pagesPerLocation": 15}
What is deliberately not collected
No email addresses, no phone numbers, no contact details of any kind. Other tools in this category sell host contact data scraped from listing text. This one does not. You get the public profile link and the business facts: how many listings, what rating, what price. Reach out through Airbnb like anyone else.
Host names are the public display names Airbnb shows on the listing page. Nothing here is private data.
Reliability, said plainly
Airbnb does not put listings in the page as ordinary links. It ships a preloaded JSON block that the browser uses to draw the page, and the listings live in there. Looking for /rooms/ links finds nothing at all, which is why this looks harder than it is.
- Measured on live pages, 6 and 7 November 2026, ten US cities with 20 pages each, three runs: 14, 34 and 39 minutes, 2,541 to 2,990 listings read, 2 to 5 lost, 240 to 287 hosts with two or more listings. A city takes about a minute when Airbnb answers normally; when it starts refusing requests, a city can take 3 to 6 minutes. A run has up to an hour, so plan on 10 cities per run.
- Direct first, proxy only when needed. Requests leave directly, which was five times faster than the datacenter proxy in our test. Anything Airbnb refuses is retried through the Apify proxy, and if direct requests keep getting refused the rest of the run switches to the proxy. You do not need to turn a proxy on.
- Hotels are left out by default, already in the search. Airbnb also lists hotel rooms: without the filter, 10 of the first 30 listings in Austin were hotels, 17 in Madrid and 21 in New York (4 November 2026). With it, every page is flats and rooms run by hosts. Turn on
includeHotelsto keep hotels. - The id that works in a listing URL is not the listing's own id. Using the wrong one returns an Airbnb "not found" page with status 200, so a run can look successful and be empty. This Actor treats a suspiciously small 200 response as not-found rather than as data.
- Every retry leaves from a different proxy exit, because retrying on an address that just refused you gets refused again.
- If the run runs out of time before a city, the log and
RUN_SUMMARYname the cities that were not processed. Nothing is dropped silently. RUN_SUMMARYreports pages served, listings found, hotels left out, how many gave a host id, how many requests Airbnb refused and how they were retried, and megabytes used.
A run finds a shared host only if it sees both listings. One page of one city will rarely find anyone. On 5 November 2026, 20 pages found 29 to 41 hosts with two or more listings in each of Austin, New York, Madrid, Miami, Los Angeles, Chicago and Nashville. In the first three, 8 pages found only 11 to 18. That is why 20, the maximum, is the default. Lower pagesPerLocation to finish faster; to cap spend, use maxResults.
minListings: 5 returns few hosts. A run compares at most about 300 listings per city, so 5 found 0 to 7 hosts per city even with 20 pages, and the biggest host had 4 to 13 of those listings. 3 found 5 to 22 per city.
Pricing
Pay per delivered row. Host rows and listing rows are charged separately, so hosts mode charges only for the rolled-up rows you asked for, not for the hundreds of listings read to build them.
Data source
Public Airbnb search and listing pages. Records describe listings and their public marketing data. No guest data and no host contact details are collected.