Channel
@Greendoor_Krasnodar
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
894subscribers
-10 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002208193388 |
|---|---|
| Type | Channel |
| Username | @Greendoor_Krasnodar |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/Greendoor_Krasnodar |
Local community — 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 19 September 2026 and assigned it the closest of 31 fixed categories, at 81% 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 |
|---|---|---|
| 13 Sept 2026, 06:18 | 894 | -3 |
| 5 Sept 2026, 07:20 | 897 | -1 |
| 29 Aug 2026, 12:43 | 898 | -4 |
| 22 Aug 2026, 09:24 | 902 | +2 |
| 14 Aug 2026, 09:27 | 900 | -1 |
| 6 Aug 2026, 23:18 | 901 | -3 |
| 6 Aug 2026, 17:32 | 904 | first reading |
6 posts held, back to 20 July 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 6 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
112 reactions across 6 posts, in 8 distinct kinds. The most used accounts for 25.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5402597777765054706 | 29 | 25.9% | |
| ❤🔥 | 23 | 20.5% | |
| 😍 | 18 | 16.1% | |
| ❤ | 16 | 14.3% | |
| 🔥 | 15 | 13.4% | |
| custom 5226968056701405877 | 7 | 6.25% | |
| 👏 | 2 | 1.79% | |
| 🤩 | 2 | 1.79% |
Custom emoji. 2 of the rows above are 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 6 of the 6 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 112 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 20 July 2026 to 5 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 54025977777650547069❤🔥4custom 52269680567014058773❤1🔥1
Video message, posted without a caption
❤🔥4custom 52269680567014058774custom 54025977777650547064
Продолжаем подглядывать за тем, как проходит экспедиция «Наследие фарфора Кубани».🐯 Вчера экспедиция побывала в гостях у ТомСойерФеста в особняке на Кирова, который сейчас реставрирует команда ТСФ. А невероятно крутая Кира Деляева рассказала о своем проекте по реставрации проекта «ФУТУРО» 💃 Да! Наша знаменитая летающая тарелка сейчас в хороших руках и проходит процесс реставрации ✅ Она скоро вернётся на прежнее мес…
😍15❤🔥9🔥6❤4
Video message, posted without a caption
🔥3❤2
Когда-то завод «Чайка» выпускал сервизы, которые сегодня бережно хранят в семьях и коллекциях. Сейчас у нас есть шанс сохранить не только фарфор, но и историю предприятия – уникальную для Кубани! ✨ Сейчас в Краснодаре проходит экспедиция «Наследие фарфора Кубани» от проекта «Открываем Россию заново». В ней участвуют 23 человека из разных городов России: архивоведы, урбанисты, искусствоведы, архитекторы-реставраторы,…
❤7custom 54025977777650547067🔥5👏2❤🔥1😍1
Сегодня в Краснодаре началась экспедиция «Наследие фарфора Кубани», важное событие для всех нас!☀️✨ ✅В предыдущих сериях: Экспедицию организует наш добрый друг, дизайнер и реставратор Тома Гущина. При поддержке других наших друзей – ТомСойейФест Краснодара. вместе с проектом «Открываем Россию заново» от программы «Больше, чем путешествие». ⭐️⭐️⭐️ Мы здесь много говорим про сохранение памяти, культуры и историческо…
custom 54025977777650547069❤🔥5❤2🤩2😍2
Showing the 6 most recent of 6 posts we hold for @Greendoor_Krasnodar. 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.
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.
Named by 6 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“Зелёная дверь Краснодара (@Greendoor_Krasnodar)” (@Greendoor_Krasnodar), 894 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/Greendoor_Krasnodar.
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.