Channel
@dachagrin
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
290subscribers
-3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002118762277 |
|---|---|
| Type | Channel |
| Username | @dachagrin |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 10 October 2026 |
| On Telegram | t.me/dachagrin |
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 23 September 2026 and assigned it the closest of 31 fixed categories, at 54% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Oct 2026, 23:00 | 290 | -1 |
| 30 Sept 2026, 10:37 | 291 | -2 |
| 30 Aug 2026, 03:12 | 293 | +2 |
| 16 Aug 2026, 18:08 | 291 | -2 |
| 8 Aug 2026, 08:16 | 293 | no change |
| 7 Aug 2026, 18:20 | 293 | first reading |
3 posts held, back to 1 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 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 3 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
111 reactions across 3 posts, in 5 distinct kinds. The most used accounts for 28.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5341530262008249365 | 32 | 28.8% | |
| custom 5325585728497807797 | 30 | 27.0% | |
| custom 5337323324361962507 | 28 | 25.2% | |
| custom 5345912082132909413 | 13 | 11.7% | |
| custom 5395331887101142132 | 8 | 7.21% |
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 3 of the 3 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 111 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 3 most recent posts we hold, published 1 August 2026 to 3 August 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.
Подружка отдала старую табуретку, лавочку и ящики, все пошкурили и всем пользуемся. Табуретка дубовая ⚡️😍 а лавочку немного изменили🙌
custom 533732332436196250721custom 534153026200824936521custom 532558572849780779718
Подружка угостила цветами, как же я благодарна🙏🙌 Дети помогают)) Вот собрала все виды флоксов. Вон тот с цветными листочками, дорогущий, что то в этом году не зацвел… Но все равно все такое красивое, ароматное💓
custom 532558572849780779712custom 534153026200824936511custom 53459120821329094136
Щипчики для колки сахара прапрабабушки 💓 Ну и детальки разные.
custom 53953318871011421328custom 53373233243619625077custom 53459120821329094137
Showing the 3 most recent of 3 posts we hold for @dachagrin. 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.
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 10 October 2026 — this entry's latest reading, not the date you are reading this.
“Дом с зеленой крышей” (@dachagrin), 290 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/dachagrin.
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.