Telegram RegisterThe public register of Telegram
Telegram profile photo for ⟨︎🎪⟩︎ - 𝟓𝟐𝟕𝟑ࣳ𝃣- 𝕳𝑜𝑚𝑒

Channel

⟨︎🎪⟩︎ - 𝟓𝟐𝟕𝟑ࣳ𝃣- 𝕳𝑜𝑚𝑒

@Dry_Home_5273

On this record: Topic · Previous handles · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

218subscribers

+13 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003935798678
TypeChannel
Username@Dry_Home_5273
Description—————————————————— 𝑆𝑇𝐴𝑅𝑇 — 10.04.2026 —————————————————— 𝕴𝑛𝑓𝑜 - @Dry_info_5273 𝕳𝑜𝑚𝑒 - @Dry_Home_5273 ——————————————————
CreatedBetween 1 April 2026 and 2 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 November 2026
Measurements held11
On Telegramt.me/Dry_Home_5273

Topic

Other / unclassifiable — 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 24 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.

Previous handles

@Dry_Home_5273 was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@lm_l1fe
held 8 August 2026 – 8 August 2026

Growth

1622181908 August 2026 — 205 subscribers8 August 2026 — 205 subscribers9 August 2026 — 206 subscribers16 August 2026 — 204 subscribers22 August 2026 — 192 subscribers29 August 2026 — 185 subscribers8 September 2026 — 180 subscribers15 September 2026 — 178 subscribers29 September 2026 — 162 subscribers8 November 2026 — 218 subscribers8 November 2026 — 218 subscribers8 August 20268 November 2026
11 measurements spanning 92 days, net +13. 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 154–226 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Nov 2026, 11:22218no change
8 Nov 2026, 10:47218+56
29 Sept 2026, 01:15162-16
15 Sept 2026, 20:56178-2
8 Sept 2026, 04:59180-5
29 Aug 2026, 01:42185-7
22 Aug 2026, 21:15192-12
16 Aug 2026, 04:58204-2
9 Aug 2026, 02:01206+1
8 Aug 2026, 11:17205no change
8 Aug 2026, 10:48205first reading

Engagement

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

ERR · 30 days
18.6%
avg views ÷ 218 subscribers
Avg views / post
40.5
20 posts measured
Reaction rate
15.9%
reactions ÷ views · ER floor
Posts in window
20
of 40 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. It is computed over the 9 of 20 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 November 2026
Posts held40 (2 August 2026 – 8 November 2026)
Views total811
Reactions total58
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Nov 2026, 11:22 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
27
Videos
68
Links
99

Lifetime counters from Telegram’s own channel header, read 8 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
19s
Average length
10s

Measured directly from 2 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.

Reaction mix

116 reactions across 16 posts, in 15 distinct kinds. The most used accounts for 19.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53617124550660999642219.0%
custom 53619734387538406902017.2%
custom 54155961269192376801210.3%
custom 5415794223695832480108.62%
custom 537549895648887555486.90%
custom 541369377423469199776.03%
custom 541560517212036549576.03%
custom 541350161739787053765.17%
custom 541366405306100462765.17%
custom 536420168496687449254.31%
custom 541608235157688447943.45%
custom 541350708059626835132.59%
custom 541598014424014339132.59%
custom 536204218829534752321.72%
custom 536205494005325354710.862%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 16 of the 40 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 116 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 40 most recent posts we hold, published 2 August 2026 to 8 November 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 20 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).

8 Nov 2026, 07:18 UTC29 views1 reactionsread 8 November 2026

😻🤩🤩▫️𝑵𝑬𝑾 𝑼𝑵𝑰𝑶𝑵➕🎁 🤩🤩🤩🤩𝐈𝐍𝐅𝐎 and 𝐋𝐈𝐅𝐄🔵 🎀🤩🤩🤩🪽🪽𝐈𝐍𝐈𝐓𝐈𝐀𝐋 :: #𝑫𝑟𝑦 #𝟓𝟐𝟕𝟑 #𝑫🎪 Мы — рады, до скрежета зубов. Рады заключить союз между проектами. Не тот союз, где жмут руки и улыбаются в камеру. Нет. Тот, где два цирка сливаются в один шатёр, и никто не выходит прежним. Мы сцепляемся. Крепко. Как челюсти. Как кольца на пальцах, которые уже не снять. Вы — огонь. Мы — бензин. Вы — бита. Мы — череп. Вместе — симфония. Это не пар…

custom 54135016173978705371

8 Nov 2026, 07:05 UTC30 views5 reactionsread 8 November 2026
Photo

🤩🤩🤩:: Закинула нфт в лайфик, мне кажется он подходит к нам. #𝖘𝖍𝖕𝕯𝖗𝖞

custom 54135016173978705372custom 54157942236958324802custom 54136640530610046271

8 Nov 2026, 07:01 UTC26 views2 reactionsread 8 November 2026

😻🤩🤩▫️𝑵𝑬𝑾 𝑼𝑵𝑰𝑶𝑵➕🎁 🤩🤩🤩🤩𝐈𝐍𝐅𝐎 and 𝐋𝐈𝐅𝐄🔵 🎀🤩🤩🤩🪽🪽𝐈𝐍𝐈𝐓𝐈𝐀𝐋 :: #𝑫𝑟𝑦 #𝟓𝟐𝟕𝟑 #𝑫🎪 Мы — рады, до скрежета зубов. Рады заключить союз между проектами. Не тот союз, где жмут руки и улыбаются в камеру. Нет. Тот, где два цирка сливаются в один шатёр, и никто не выходит прежним. Мы сцепляемся. Крепко. Как челюсти. Как кольца на пальцах, которые уже не снять. Вы — огонь. Мы — бензин. Вы — бита. Мы — череп. Вместе — симфония. Это не пар…

custom 54135070805962683511custom 54155961269192376801

8 Nov 2026, 06:38 UTC32 views7 reactionsread 8 November 2026

😻🤩🤩▫️𝑰𝑵𝑻𝑬𝑹𝑨𝑪𝑻𝑰𝑽𝑬➕🎁 🤩🥩🥩🤩::наши участники выполнили интерактив!! Ты слышишь, как что-то катится по плитке. Сначала ты думаешь — мяч. Потом понимаешь:: это его голова. Голова клоуна, который ввёл интерактивное представление. Без грима. Везде пахнет карамелью, медью и мертвечиной... 🤩🤩🤩🤩🥩🥩🥩🥩💎 🎀🤩🤩🤩🪽🪽𝐈𝐍𝐈𝐓𝐈𝐀𝐋 :: #𝑫𝑟𝑦 #𝟓𝟐𝟕𝟑 #𝑫🎪 🤩🤩#𝖗𝖊𝖘𝖚𝖑𝖙𝖘𝕯𝖗𝖞 🥩🥩#𝖎𝖓𝖙𝖊𝖗𝖆𝖈𝖙𝖎𝖛𝖊𝕯𝖗𝖞 Смех не стихал, даже когда трещали кости. Грим не тек — он врастал…

custom 54136640530610046272custom 54155961269192376802custom 54157942236958324802custom 54136937742346919971

8 Nov 2026, 06:33 UTC30 views7 reactionsread 8 November 2026

😻🤩🤩▫️𝑯𝑬𝑨𝑫𝑰𝑵𝑮➕🎁 🥹🤩🤩🤩 𝐔𝐒 𝐂𝐎𝐑𝐄 ❤️ 🎀🤩🤩🤩🪽🪽𝐈𝐍𝐈𝐓𝐈𝐀𝐋 :: #𝑫𝑟𝑦 #𝟓𝟐𝟕𝟑 #𝑫🎪 🤩🤩KAMISAMA KISS - Tomoe & Nanami Momozono #𝖍𝖊𝖆𝖉𝖎𝖓𝖌𝕯𝖗𝖞 🌟🤩🌟🤍#️⃣

custom 54136937742346919972custom 54155961269192376802custom 54135016173978705371custom 54135070805962683511custom 54157942236958324801

8 Nov 2026, 06:19 UTC29 views6 reactionsread 8 November 2026

😻🤩🤩▫️𝑵𝑬𝑾 𝑼𝑵𝑰𝑶𝑵➕🎁 🤩🤩🤩🤩𝐈𝐍𝐅𝐎 and 𝐋𝐈𝐅𝐄🔵 🎀🤩🤩🤩🪽🪽𝐈𝐍𝐈𝐓𝐈𝐀𝐋 :: #𝑫𝑟𝑦 #𝟓𝟐𝟕𝟑 #𝑫🎪 Мы — рады, до скрежета зубов. Рады заключить союз между проектами. Не тот союз, где жмут руки и улыбаются в камеру. Нет. Тот, где два цирка сливаются в один шатёр, и никто не выходит прежним. Мы сцепляемся. Крепко. Как челюсти. Как кольца на пальцах, которые уже не снять. Вы — огонь. Мы — бензин. Вы — бита. Мы — череп. Вместе — симфония. Это не пар…

custom 54157942236958324802custom 54135016173978705371custom 54136640530610046271custom 54155961269192376801custom 54159801442401433911

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

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

“⟨︎🎪⟩︎ - 𝟓𝟐𝟕𝟑ࣳ𝃣- 𝕳𝑜𝑚𝑒” (@Dry_Home_5273), 218 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/Dry_Home_5273.

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.