#CityEngine
Live, measured metrics for the hashtag #CityEngine from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #cityengine
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 · fosstodon.org (Mastodon public tags API) · fetched 2026-07-28 19:13 UTC1 uses by 1 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-28 19:13 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 19:13 UTCEverything below is measured over the latest 33 public posts (spanning ~32788 hours).
Posting hours (UTC) — busiest: 11:00
Languages: English (33)
Avg boosts / post: 0.2
Top of the latest posts
Hurrrah! one company has booked 4 2-day #ArcGIS #CityEngine training sessions. Not the biggest booking I've had but definitely up there. #GIS #Planning #UrbanDesign
In Nottingham (UK) today for 3 days teaching #cityengine to a lovely client. Invariably we will discuss #gameengines and #digitaltwins #geodesign and #3D #GIS 😀
My latest blog post… “Is this the end of #CityEngine as we know it? (2026.0 and the #Python 3 era)” https://www.geoplanit.co.uk/?p=6334
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/cityengine