Telegram RegisterThe public register of Telegram
Telegram profile photo for Very SAUCE 💙

Channel

Very SAUCE 💙

@tgm_dk

Has discussion group

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

4,985subscribers

+28 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-1002244616977
TypeChannel
Username@tgm_dk
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded1 September 2026
Last confirmed live2 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/tgm_dk

Growth

4,9355,0024,968.57 August 2026 — 4,957 subscribers8 August 2026 — 4,953 subscribers10 August 2026 — 4,935 subscribers14 August 2026 — 4,954 subscribers17 August 2026 — 5,002 subscribers21 August 2026 — 4,993 subscribers24 August 2026 — 4,973 subscribers27 August 2026 — 4,960 subscribers30 August 2026 — 4,968 subscribers1 September 2026 — 4,968 subscribers2 September 2026 — 4,985 subscribers4,9857 August 20262 September 2026
11 measurements spanning 25 days, net +28. 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 4,925–5,012 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Sept 2026, 05:354,985+17
1 Sept 2026, 21:514,968no change
30 Aug 2026, 11:174,968+8
27 Aug 2026, 20:554,960-13
24 Aug 2026, 22:434,973-20
21 Aug 2026, 02:054,993-9
17 Aug 2026, 19:565,002+48
14 Aug 2026, 16:334,954+19
10 Aug 2026, 21:424,935-18
8 Aug 2026, 06:004,953-4
7 Aug 2026, 17:584,957first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

Forward network

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

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

“Very SAUCE 💙” (@tgm_dk), 4,985 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/tgm_dk.

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.