Telegram RegisterThe public register of Telegram
Telegram profile photo for Ping99ms

Channel

Ping99ms

@ping99ms

On this record: Topic · Growth · Engagement · Cite this entry

9,261subscribers

-422 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001865693068
TypeChannel
Username@ping99ms
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded23 August 2026
Last confirmed live20 October 2026
Measurements held20
Confirmed unchanged1 time, most recently 20 October 2026
On Telegramt.me/ping99ms

Topic

Other / unclassifiable — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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

9,2619,6839,4727 August 2026 — 9,683 subscribers7 August 2026 — 9,681 subscribers10 August 2026 — 9,660 subscribers14 August 2026 — 9,642 subscribers17 August 2026 — 9,603 subscribers20 August 2026 — 9,578 subscribers23 August 2026 — 9,578 subscribers24 August 2026 — 9,555 subscribers27 August 2026 — 9,536 subscribers30 August 2026 — 9,510 subscribers2 September 2026 — 9,493 subscribers7 September 2026 — 9,474 subscribers11 September 2026 — 9,458 subscribers15 September 2026 — 9,441 subscribers25 September 2026 — 9,411 subscribers4 October 2026 — 9,362 subscribers10 October 2026 — 9,329 subscribers14 October 2026 — 9,312 subscribers16 October 2026 — 9,285 subscribers20 October 2026 — 9,261 subscribers7 August 202620 October 2026
20 measurements spanning 74 days, net -422. 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 9,198–9,746 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
20 Oct 2026, 05:299,261-24
16 Oct 2026, 19:179,285-27
14 Oct 2026, 05:289,312-17
10 Oct 2026, 15:199,329-33
4 Oct 2026, 21:599,362-49
25 Sept 2026, 10:019,411-30
15 Sept 2026, 15:379,441-17
11 Sept 2026, 17:419,458-16
7 Sept 2026, 04:189,474-19
2 Sept 2026, 19:379,493-17
30 Aug 2026, 17:349,510-26
27 Aug 2026, 09:539,536-19
24 Aug 2026, 03:259,555-23
23 Aug 2026, 18:229,578no change
20 Aug 2026, 09:529,578-25
17 Aug 2026, 12:049,603-39
14 Aug 2026, 04:069,642-18
10 Aug 2026, 15:279,660-21
7 Aug 2026, 16:349,681-2
7 Aug 2026, 09:409,683first reading

Engagement

No public post preview. We read this entry on 24 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

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 20 October 2026 — this entry's latest reading, not the date you are reading this.

“Ping99ms” (@ping99ms), 9,261 subscribers as measured 20 October 2026. Telegram Register, tgregister.com/channel/ping99ms.

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.