Telegram RegisterThe public register of Telegram
Telegram profile photo for dom.radugi | путешествия | автодом

Channel

dom.radugi | путешествия | автодом

@domradugimuz

Has discussion group

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

1,520subscribers

-12 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001377273727
TypeChannel
Username@domradugimuz
CreatedBetween 1 April 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded27 September 2026
Last confirmed live1 November 2026
Measurements held21
Confirmed unchanged2 times, most recently 1 November 2026
On Telegramt.me/domradugimuz

Topic

Travel — 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 27 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 the other topics.

Growth

1,5191,5331,5267 August 2026 — 1,532 subscribers10 August 2026 — 1,533 subscribers13 August 2026 — 1,531 subscribers16 August 2026 — 1,529 subscribers19 August 2026 — 1,530 subscribers23 August 2026 — 1,529 subscribers25 August 2026 — 1,530 subscribers28 August 2026 — 1,529 subscribers31 August 2026 — 1,527 subscribers3 September 2026 — 1,526 subscribers8 September 2026 — 1,529 subscribers12 September 2026 — 1,530 subscribers16 September 2026 — 1,531 subscribers27 September 2026 — 1,531 subscribers2 October 2026 — 1,525 subscribers8 October 2026 — 1,526 subscribers13 October 2026 — 1,523 subscribers16 October 2026 — 1,520 subscribers19 October 2026 — 1,521 subscribers26 October 2026 — 1,519 subscribers29 October 2026 — 1,520 subscribers1,5207 August 202629 October 2026
21 measurements spanning 82 days, net -12. 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,517–1,535 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 21
Measured (UTC)SubscribersChange
29 Oct 2026, 02:551,520+1
26 Oct 2026, 00:151,519-2
19 Oct 2026, 15:401,521+1
16 Oct 2026, 18:071,520-3
13 Oct 2026, 22:061,523-3
8 Oct 2026, 17:201,526+1
2 Oct 2026, 07:001,525-6
27 Sept 2026, 16:151,531no change
16 Sept 2026, 07:411,531+1
12 Sept 2026, 12:201,530+1
8 Sept 2026, 06:191,529+3
3 Sept 2026, 00:321,526-1
31 Aug 2026, 02:531,527-2
28 Aug 2026, 11:481,529-1
25 Aug 2026, 19:421,530+1
23 Aug 2026, 00:361,529-1
19 Aug 2026, 16:231,530+1
16 Aug 2026, 20:531,529-2
13 Aug 2026, 18:261,531-2
10 Aug 2026, 21:121,533first 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.

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

“dom.radugi | путешествия | автодом” (@domradugimuz), 1,520 subscribers as measured 29 October 2026. Telegram Register, tgregister.com/channel/domradugimuz.

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.