Telegram RegisterThe public register of Telegram
Telegram profile photo for CoMaps

Channel

CoMaps

@CoMapsApp

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cross-platform identity · Cite this entry

868subscribers

+19 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002629877151
TypeChannel
Username@CoMapsApp
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live3 October 2026
Measurements held9
Confirmed unchanged1 time, most recently 3 October 2026
On Telegramt.me/CoMapsApp

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 19 September 2026 and assigned it the closest of 31 fixed categories, at 96% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

849868858.57 August 2026 — 849 subscribers8 August 2026 — 849 subscribers8 August 2026 — 850 subscribers16 August 2026 — 853 subscribers24 August 2026 — 858 subscribers31 August 2026 — 859 subscribers10 September 2026 — 863 subscribers17 September 2026 — 865 subscribers3 October 2026 — 868 subscribers7 August 20263 October 2026
9 measurements spanning 57 days, net +19. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 846–871 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Oct 2026, 10:17868+3
17 Sept 2026, 14:40865+2
10 Sept 2026, 09:58863+4
31 Aug 2026, 23:49859+1
24 Aug 2026, 18:24858+5
16 Aug 2026, 15:45853+3
8 Aug 2026, 16:54850+1
8 Aug 2026, 01:19849no change
7 Aug 2026, 20:37849first reading

Engagement

20 posts held, back to 20 June 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

487 reactions across 19 posts, in 12 distinct kinds. The most used accounts for 46.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤22446.0%
👍9118.7%
⚡6312.9%
🎉346.98%
🙏224.52%
🔥183.70%
🥰163.29%
👏122.46%
🤨30.616%
🤯20.411%
😭10.205%
🤔10.205%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 19 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 487 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 20 June 2026 to 7 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

7 Aug 2026, 12:17 UTC258 views10 reactionsread 8 August 2026
Photo

Are you attending the State of the Map conference in Paris at the end of August? Some of us will be there as well and give a talk about CoMaps. We'd love to also organize a small meet-up with folks who are interested to get to know us and each other! Depending on the number of folks, that could be over a beverage or a meal. Join our 'cafe' chat room if that sounds interesting and we'll plan it there. Find details o…

🥰6👍3⚡1

Signed Bastian Greshake Tzovaras

7 Aug 2026, 04:48 UTC358 views9 reactionsread 8 August 2026
File

A hotfix 2026.08.07-3 Android release! 🤖 https://codeberg.org/comaps/comaps/releases/tag/v2026.08.07-3 Its a follow-up to the 2026.07.16-10 release (check full changelog there). • Fixed crash during navigation when app is opened after running in the background for a long time - by @LMBishop #4762 It will be available soon on Google Play and F-Droid. (same hotfix for iOS had been previously released as 2026.07.25)

👍8⚡1

Signed pastk

5 Aug 2026, 12:24 UTC387 views29 reactionsread 8 August 2026
Photo

New maps with OpenStreetMap data from August 3 are now available for download. Press "check for updates" in the map download screen to see them!

👍24🎉3❤2

Signed Bastian Greshake Tzovaras

30 Jul 2026, 14:03 UTC776 views20 reactionsread 8 August 2026
Photo

New maps with #OpenStreetMap data from July 28th are out now. Press "check for updates" in the map download screen to see them! If you're getting CoMaps via Google Play: Make sure you're already on release 2026.07.16 that only came out there yesterday!

🎉12⚡4👍4

Signed Bastian Greshake Tzovaras

30 Jul 2026, 00:29 UTC747 views27 reactionsread 8 August 2026
Photo

After Google Play took its time, release 2026.07.16 is finally out on all platforms. Among other things, it includes lane guidance on iOS/CarPlay, a route preview screen and many more. See https://codeberg.org/comaps/comaps/releases/tag/v2026.07.16-10 for the full list of changes!

🎉15⚡6❤6

Signed Bastian Greshake Tzovaras

29 Jul 2026, 12:38 UTC639 views27 reactionsread 8 August 2026
Photo

Merci to the folks at Framasoft for making Framastart, which lists ethical and accessible digital tools. And we made it on their list of suggested smartphone apps! 🗺 You can explore more alternatives on their website: https:// framastart.org/

❤17👍5👏4⚡1

Signed Bastian Greshake Tzovaras

24 Jul 2026, 03:55 UTC865 views15 reactionsread 8 August 2026

CoMaps is currently seeking an umbrella organization to join in order to better position itself as a project. The team has shortlisted two options and is currently gathering community feedback on which might be a better fit. Learn more and state your preference: https://codeberg.org/comaps/Governance/issues/166 (the poll closes end of day 31 July)

❤13⚡2

Signed pastk

23 Jul 2026, 14:10 UTC853 views29 reactionsread 8 August 2026
Photo

New maps with OpenStreetMap data from July 21st data are out. Press "check for updates" in the map download screen to see them!

❤21⚡6👍2

Signed Bastian Greshake Tzovaras

22 Jul 2026, 14:06 UTC932 views62 reactionsread 8 August 2026
Photo

By the total number of edits made, CoMaps was the 15th most used OpenStreetMap editor in June. At first glance, that might not sound like a lot, but: With that, we are the #1 OSM editor that is not mainly an editor but a fully fledged map & navigation app and also editor! From the start we have said that we want CoMaps to be a good citizen of the larger OSM ecosystem and make sure that we and our users contribute b…

❤38👍9🔥5🥰4⚡2🎉2👏2

Signed Bastian Greshake Tzovaras

16 Jul 2026, 08:45 UTC≈1,040 views25 reactionsread 8 August 2026

July 14 maps are bundled with the above 2026.07.16-10 release. Please update the app first to get the new maps, older app releases won't be able to update to these July 14 or any later maps as these new maps contain incompatible changes.

⚡13❤6👍3🤨3

Signed pastk

16 Jul 2026, 08:41 UTC≈1,040 views27 reactionsread 8 August 2026
File

A new 2026.07.16-10 release! 🎉 • Turn-by-turn navigation directions preview • Added road shields to next turn direction signs and improved turn descriptions • Improved turn instructions for roundabouts, U-turns and other cases • Rotate the map slightly towards route while in driving navigation • Display numbers of parking spaces with electric chargers and for disabled drivers • Added stages, animal boarding places a…

❤20⚡6😭1

Signed pastk

11 Jul 2026, 20:08 UTC969 views17 reactionsread 8 August 2026
File

New Android test build 2026.07.11-42-test 🤖 https://codeberg.org/comaps/comaps/issues/4733 Please test and provide feedback on following changes: - Added road shields to next turn direction signs and improved turn descriptions - by @AndrewShkrob via OM and @LMBishop #4619 - A bar with enabled routing options (tap an option to disable it) and a quick access button in the route building screen - @nilshasler #4648 - Bl…

❤10⚡6👍1

Signed pastk

Showing the 12 most recent of 20 posts we hold for @CoMapsApp. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cross-platform identity — Wikidata

A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.

Q134374059 on Wikidata, read 11 October 2026
LabelNo label recorded on this Wikidata item
Descriptionfree and open source map & navigation app; community fork of Organic Maps
X / Twitter@comapsapp
Official sitehttps://www.comaps.app/

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 3 October 2026 — this entry's latest reading, not the date you are reading this.

“CoMaps” (@CoMapsApp), 868 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/CoMapsApp.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.