There is no honest single figure, and we are not going to invent one. Two similar-looking properties on the same street can land far apart because of size, availability, season, price and what it costs to run them. The question worth answering is not what the average host makes — it is what this specific property clears at realistic prices and realistic nights sold. That one you can compute.
None of these are exotic and all of them are routinely left out of the figures people compare themselves against.
Keeping these in one place month by month is most of the work. If you do not already have a sheet for it, there is a free income and expense tracker layout you can copy.
An average is a single number standing in for a pile of properties that have almost nothing in common. Six things get flattened out of it, and every one of them can move your result more than the average itself.
There is a second problem behind all six. Nobody outside the booking platforms can see what a guest actually paid, so any figure describing what hosts earn is inferred from calendars and asking prices rather than read from books. Tools that publish it model it. We do not publish it at all — see how accurate those estimates are.
Build three cases, not one: a cautious month, a normal month and a peak month. Use the revenue calculator to turn rate and occupancy into an annual figure, the occupancy calculator to check that the occupancy you assumed is one you have actually achieved, and the nightly rate calculator to work backwards from a payout you need.
Then ground the rate assumption. What comparable places in your own city ask for specific future nights is public and checkable: similar area, similar bedroom count, similar capacity and standard. We read those asking prices from live listing pages on Booking.com and Agoda when you run a scan, and we never forecast what they will do next. An asking price is not proof anyone booked at it — but it is a real number about your street, which is more than any national average can offer.