Channel
@dom10c39
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
323subscribers
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002196975047 |
|---|---|
| Type | Channel |
| Username | @dom10c39 |
| Description | Авторский канал про "Краснодар" |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 1 |
| On Telegram | t.me/dom10c39 |
Growth history is still building. We hold one measurement for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 17:45 | 323 | first reading |
20 posts held, back to 19 April 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 pageof 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 20 posts for this entry, the most recent from 8 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 14 August 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.
Measured directly from 1 video 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.
174 reactions across 20 posts, in 15 distinct kinds. The most used accounts for 43.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 75 | 43.1% | |
| 👎 | 20 | 11.5% | |
| 👍 | 16 | 9.20% | |
| 🙏 | 12 | 6.90% | |
| ❤🔥 | 11 | 6.32% | |
| custom 5294086601557693249 | 8 | 4.60% | |
| 💔 | 8 | 4.60% | |
| 🤣 | 8 | 4.60% | |
| 🔥 | 5 | 2.87% | |
| 😍 | 4 | 2.30% | |
| 🏆 | 2 | 1.15% | |
| 💘 | 2 | 1.15% | |
| ⚡ | 1 | 0.575% | |
| 😢 | 1 | 0.575% | |
| 🤡 | 1 | 0.575% |
Custom emoji. One 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 count beside it isTelegram’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 20 of the 20 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 174reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 19 April 2026 to 8 June 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.
Уже скоро новый сезон,так что держите предполагаемый состав на предстоящий сезон. Новые трансферы Каноббио-топовый лв за не совсем большую цену,идеальная замена Виктору Са,очень большие слухи по этому игроку. Бобадилло-хороший парагвайский цп,отличный игрок для замены,игрок для кубка явно. Олаи-очень перспективный молодой игрок,хорошо заменит Козлова. Уходы: Ленини-очень много слухов про его уход,Олаи хорошая замена…
😍4
Спасибо тебе.
custom 52940866015576932498🤣2👍1
Все..
🏆2⚡1
Кубок должен быть в Краснодаре💚🖤
🙏8❤1🤣1
🤯 САФОНОВ МОЖЕТ СТАТЬ ОДНОКЛУБНИКОМ РОНАЛДУ! ⚽️ Делегация «Аль-Насра» отправится на финал ЛЧ против, чтобы оценить голкипера 💶 «ПСЖ» готов расстаться с вратарём за сумму в €35 млн
👎13
Уже через 2 дня играем суперфинал Какие ожидания?
❤4😢1
Нету смысла растраиваться , шикарно отыграли , зенит выиграл СУПЕР позорную победу, с пенальти бля , мы очень достойно отыграли сезон , лжечемпион пусть празднует до июля , А у Зенита всегда пенальти , Не помните матч Зенит - Спартак Там Зенит выиграл 2:0 , и угадайте как он забил? Конечно же с пенальти , как и сегодня , Всех с победой , всех с сезоном , впереди кубок . КРАСНОДАР ВСЕГДА БУДЕТ ПЕРВЫЙ👊
❤16🔥1🤣1
Верим🤞
❤6💔1
💔
❤4💔4👍1
Уже через час играем свой финал , верим в победу🙏
❤3
🍌 https://vt.tiktok.com/ZS9Gv2tjm/
👍3❤2
Тюкавин о предстоящей игре с Краснодаром: На данном этапе это будет самый принципиальный матч для нас! Обыграем «принципиальных» во второй раз?)
👍5👎2🤣2❤1🤡1
Showing the 12 most recent of 20 posts we hold for @dom10c39. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“Дом 10 строение 39” (@dom10c39), 323 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/dom10c39.
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.