Telegram RegisterThe public register of Telegram
Telegram profile photo for gadji_q

Channel

gadji_q

@gadji_q

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

8,351subscribers

-740 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1001660636166
TypeChannel
Username@gadji_q
Description-Не прекращай бороться за свои мечты @
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live4 November 2026
Measurements held24
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/gadji_q

Topic

Religion — 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 85% 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 the other topics.

Growth

8,3519,0918,7219 August 2026 — 9,091 subscribers10 August 2026 — 9,082 subscribers13 August 2026 — 9,064 subscribers16 August 2026 — 9,040 subscribers19 August 2026 — 9,022 subscribers23 August 2026 — 8,987 subscribers26 August 2026 — 8,932 subscribers29 August 2026 — 8,900 subscribers1 September 2026 — 8,857 subscribers6 September 2026 — 8,801 subscribers10 September 2026 — 8,736 subscribers14 September 2026 — 8,710 subscribers18 September 2026 — 8,682 subscribers27 September 2026 — 8,599 subscribers5 October 2026 — 8,552 subscribers11 October 2026 — 8,517 subscribers14 October 2026 — 8,488 subscribers17 October 2026 — 8,460 subscribers20 October 2026 — 8,435 subscribers23 October 2026 — 8,411 subscribers26 October 2026 — 8,396 subscribers29 October 2026 — 8,383 subscribers1 November 2026 — 8,362 subscribers4 November 2026 — 8,351 subscribers9 August 20264 November 2026
24 measurements spanning 87 days, net -740. 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 8,240–9,202 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 24
Measured (UTC)SubscribersChange
4 Nov 2026, 16:078,351-11
1 Nov 2026, 09:368,362-21
29 Oct 2026, 04:198,383-13
26 Oct 2026, 07:168,396-15
23 Oct 2026, 10:568,411-24
20 Oct 2026, 14:008,435-25
17 Oct 2026, 12:508,460-28
14 Oct 2026, 10:508,488-29
11 Oct 2026, 06:558,517-35
5 Oct 2026, 06:568,552-47
27 Sept 2026, 07:198,599-83
18 Sept 2026, 10:578,682-28
14 Sept 2026, 03:408,710-26
10 Sept 2026, 19:208,736-65
6 Sept 2026, 02:558,801-56
1 Sept 2026, 16:238,857-43
29 Aug 2026, 15:568,900-32
26 Aug 2026, 08:078,932-55
23 Aug 2026, 15:168,987-35
19 Aug 2026, 15:529,022first reading

Engagement

43 posts held, back to 16 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 30 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
13.1%
avg views ÷ 8,351 subscribers
Avg views / post
1,090
3 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
3
of 43 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 15 October 2026
Posts held43 (16 May 2026 – 15 October 2026)
Views total3,284
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken4 Nov 2026, 23:04 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
≈1,430
Videos
≈312
Links
≈10

Lifetime counters from Telegram’s own channel header, read 4 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
2m 52s
Average length
17s

Measured directly from 10 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 3 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

15 Oct 2026, 21:10 UTC804 viewsread 4 November 2026

как же прекрасны сердца тех, кто, проходя через самые ужасные жизненные штормы, все же выбирает оставаться нежным, тихим, терпеливым, добрым и смиренным они выигрывают дважды - в этой жизни и в следующей.

11 Oct 2026, 20:50 UTC≈1,150 viewsread 4 November 2026

Люди погибли, пребывая в двух крайностях: в излишестве денег и в излишестве речи

7 Oct 2026, 21:10 UTC≈1,330 viewsread 4 November 2026

красив мир у того, у кого сердце и душа соприкасаются с добротой

5 Oct 2026, 22:10 UTC≈1,410 viewsread 4 November 2026

в конечном итоге ты будешь разочарован, если ты думаешь, что люди будут делать для тебя тоже самое, что и ты для них, не у всех такое же сердце, как у тебя

25 Sept 2026, 18:53 UTC≈1,680 viewsread 4 November 2026

не понимаю, как люди притворяются, что у них хорошее настроение, если меня что-то бесит, мое недовольное лицо светится ярче маяка

17 Sept 2026, 20:28 UTC≈2,250 viewsread 4 November 2026

لا تَدَعِ القَلَقَ يُثْقِلُ قَلْبَكَ، فَكُلُّ شَيْءٍ سَيَأْتِي فِي وَقْتِهِ Не позволяй тревоге утяжелять сердце - всё приходит в своё время.

16 Sept 2026, 19:04 UTC≈1,940 viewsread 4 November 2026
Photo

Походу, я всё-таки не так уж и плох😂

6 Sept 2026, 17:37 UTC≈2,170 viewsread 4 November 2026

выбор правильного решения приходит с опытом, опыт приходит с каждым неправильным выбором

1 Sept 2026, 19:27 UTC≈1,840 viewsread 4 November 2026

всегда найдётся человек, который поступит с тобой так же, как ты когда-то поступил с другим - и это будет самым честным зеркалом твоей души ))

31 Aug 2026, 19:52 UTC≈1,720 viewsread 4 November 2026
Photo

ничего не ждать и ни о чем не жалеть. должное придёт. случившееся неизменно))

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

Posts recorded as deleted after publishing

We recorded 3 posts on @gadji_q as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
24 August 2026
Most recent seen missing
25 August 2026
Median time before seen missing
32 hours
Seen missing in the last 30 days
0

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

MERZA_BEZAMM♥️
@merzabezamm1 · 53,781
Telegram ranks this channel #29 of 41 here — alongside 40 others — read 26 August 2026
Чеченские песни / Чеченская Музыка
@chechen_musics · 74,854
Telegram ranks this channel #33 of 51 here — alongside 50 others — read 19 August 2026
Чеченские новые песни 2026 🎶🔊
@elizoveta_66 · 86,920
Telegram ranks this channel #40 of 47 here — alongside 46 others — read 18 August 2026

This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“gadji_q” (@gadji_q), 8,351 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/gadji_q.

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.