Telegram RegisterThe public register of Telegram

Channel

.gps

@gupose

On this record: Growth · Engagement · Posts · Citations · Cite this entry

858subscribers

-1 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1002145269522
TypeChannel
Username@gupose
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 9 August 2026
On Telegramt.me/gupose

Growth

858859858.59 Aug 2026, 10:55 — 859 subscribers9 Aug 2026, 11:00 — 859 subscribers9 Aug 2026, 21:21 — 858 subscribers9 Aug 2026, 10:559 Aug 2026, 21:21
3 measurements taken within a single day, net -1. 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 858–859 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 21:21858-1
9 Aug 2026, 11:00859no change
9 Aug 2026, 10:55859first reading

Engagement

17 posts held, back to 8 May 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 pageof 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 17 posts for this entry, the most recent from 20 June 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

12 Jun 2026, 14:25 UTC≈1,500 viewsread 9 August 2026

держа пепел в ладонях, продолжаю бороться с пламенем, а огня давно нет. неужели исчезло?

Showing the 12 most recent of 17 posts we hold for @gupose. 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.

msnd.
@msndmsnd · 4,9181 postwrong/gateway .₅₀₂
@wronggateway502 · 3651 post

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.

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

“.gps” (@gupose), 858 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/gupose.

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.