#itineraryplanning
Live, measured metrics for the hashtag #itineraryplanning from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #itineraryplanning
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · mastodon.online (Mastodon public tags API) · fetched 2026-11-22 15:13 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-11-22 15:13 UTCNo related tags with measured usage found for #itineraryplanning.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-11-22 15:13 UTCEverything below is measured over the latest 10 public posts (spanning ~3104 hours).
Posting hours (UTC)
Languages: English (10)
Avg boosts / post: 0
Top of the latest posts
Fourteen days for Southeast Asia is the right minimum for a focused first trip. The classic mistake: trying to fit Vietnam + Thailand + Cambodia + Singapore + Malaysia + Indonesia in 14 days. #ItineraryPlanning https://compassdraft.com/14-d
The 3-day weekend is the most-common short-trip format. Friday evening to Sunday evening; long weekends extending Thursday-Monday. #ItineraryPlanning https://compassdraft.com/how-to-plan-3-day-weekend-getaway-2026?utm_source=mastodon&utm_me
Seven days is the right length for a focused first Mexico trip if you resist the temptation to add beach destinations + the Yucatán to a Mexico City + Oaxaca itinerary. #ItineraryPlanning https://compassdraft.com/7-day-mexico-itinerary-mexi
#itineraryplanning across platforms
every network with a public tag surfaceFollow #itineraryplanning straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/itineraryplanning