Telegram RegisterThe public register of Telegram
Telegram profile photo for ♥️❦ نـوی غٖٜمٖٜجٖٜنٖٜی تٖٜرانٖٜي ٜٜ ❦♥️

Channel

♥️❦ نـوی غٖٜمٖٜجٖٜنٖٜی تٖٜرانٖٜي ٜٜ ❦♥️

@GhmgneTrane313

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

1,584subscribers

+91 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1002468335317
TypeChannel
Username@GhmgneTrane313
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded26 September 2026
Last confirmed live27 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 27 September 2026
On Telegramt.me/GhmgneTrane313

Topic

Music — 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 26 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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

1,4911,5841,537.59 August 2026 — 1,493 subscribers10 August 2026 — 1,492 subscribers13 August 2026 — 1,491 subscribers16 August 2026 — 1,496 subscribers19 August 2026 — 1,497 subscribers23 August 2026 — 1,501 subscribers25 August 2026 — 1,517 subscribers28 August 2026 — 1,515 subscribers31 August 2026 — 1,519 subscribers4 September 2026 — 1,545 subscribers13 September 2026 — 1,558 subscribers17 September 2026 — 1,580 subscribers26 September 2026 — 1,580 subscribers27 September 2026 — 1,584 subscribers9 August 202627 September 2026
14 measurements spanning 49 days, net +91. 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 1,477–1,598 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Sept 2026, 06:551,584+4
26 Sept 2026, 16:471,580no change
17 Sept 2026, 16:581,580+22
13 Sept 2026, 13:581,558+13
4 Sept 2026, 10:581,545+26
31 Aug 2026, 14:181,519+4
28 Aug 2026, 20:331,515-2
25 Aug 2026, 21:061,517+16
23 Aug 2026, 02:061,501+4
19 Aug 2026, 15:171,497+1
16 Aug 2026, 22:051,496+5
13 Aug 2026, 23:591,491-1
10 Aug 2026, 09:201,492-1
9 Aug 2026, 09:151,493first 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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

“♥️❦ نـوی غٖٜمٖٜجٖٜنٖٜی تٖٜرانٖٜي ٜٜ ❦♥️” (@GhmgneTrane313), 1,584 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/GhmgneTrane313.

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.