SPACEBOOKING Увидимся уже завтра на концерте Uglystephan, осталось менее 50 билетов • Самара | 21 августа — Это будет крутое шоу, наполненное любовью и атмосферой ♾
custom 53370378464757201656custom 53729170411938288495custom 53572906874505915624

Channel
@spacesbooking
On this record: Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
7,534subscribers
+188 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002720766960 |
|---|---|
| Type | Channel |
| Username | @spacesbooking |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 5 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 5 September 2026 |
| On Telegram | t.me/spacesbooking |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Sept 2026, 17:20 | 7,534 | +399 |
| 2 Sept 2026, 02:37 | 7,135 | -27 |
| 29 Aug 2026, 22:55 | 7,162 | -28 |
| 26 Aug 2026, 16:54 | 7,190 | -17 |
| 23 Aug 2026, 14:56 | 7,207 | -53 |
| 19 Aug 2026, 14:27 | 7,260 | -11 |
| 16 Aug 2026, 16:06 | 7,271 | -41 |
| 12 Aug 2026, 13:37 | 7,312 | +11 |
| 9 Aug 2026, 13:21 | 7,301 | -37 |
| 6 Aug 2026, 18:28 | 7,338 | -8 |
| 6 Aug 2026, 08:47 | 7,346 | first reading |
28 posts held, back to 12 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 16 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 20 August 2026 |
|---|---|
| Posts held | 28 (12 July 2026 – 20 August 2026) |
| Views total | 16,609 |
| Reactions total | 103 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 20 Aug 2026, 13:05 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.
1,768 reactions across 26 posts, in 4 distinct kinds. The most used accounts for 32.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5307670152890826839 | 571 | 32.3% | |
| custom 5337037846475720165 | 528 | 29.9% | |
| custom 5357290687450591562 | 380 | 21.5% | |
| custom 5372917041193828849 | 289 | 16.3% |
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 26 of the 28 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 1,768 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 28 most recent posts we hold, published 12 July 2026 to 20 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.
SPACEBOOKING Увидимся уже завтра на концерте Uglystephan, осталось менее 50 билетов • Самара | 21 августа — Это будет крутое шоу, наполненное любовью и атмосферой ♾
custom 53370378464757201656custom 53729170411938288495custom 53572906874505915624
28 августа
custom 53572906874505915629custom 53076701528908268393custom 53370378464757201652
LAST SUMMER PARTY | ЧС ♾ Последние теплые вечера созданы для того, чтобы проводить их вместе. Подарим этому лету красивый финал с возвращением Чистых Сердец! — Date: 29.08 — Place: ул. Профсоюзная, 26, club «Bazzar» — Time: 18:00-21:00 — FC/DC 14+ 🟢 Чистые в TG! 🎫 Билеты: ЗАЛЕТАЙ Казань!
custom 53370378464757201654custom 53076701528908268393custom 53729170411938288492
🎉 Результаты розыгрыша: 🏆 Победители: 1. Милкис (@mmmilkisssss) 2. элuзoчкa (@mewhub) 3. менеджер колбасы (@MrSecret299) 4. Trape…tutututu (@IvanGordiq) 5. wwht (@aggwwi) ✔️Проверить результаты
custom 53076701528908268396custom 53370378464757201653custom 53729170411938288492
Наши хорошие друзья делают тур с Voskresenskii — Всех будем ждать на данных концертах Женя впервые отправляется в тур и уже готов зарядить тебя своим лайвом, советуем не пропускать данное событие! 🎫 БИЛЕТЫ НА САЙТЕ Промокод «SPACE»
custom 53370378464757201657custom 53076701528908268396custom 53572906874505915624custom 53729170411938288492
SPACEBOOKING | КОНКУРС — Призы: 💥 1 место — BACKSTAGE на концерт (парный) 💥 2 место — Meet&Greet с артистом + такси туда-обратно 💥 3-5 место — Одиночный билет на любой из концертов сетки ‼️ Условия предельно простые: • Подписаться на наш канал –> @spacesbooking — Результаты розыгрыша будут подводиться 13 августа в 20:00 🔜 📍 Билеты на наши концерты
custom 53076701528908268399custom 53572906874505915627custom 53370378464757201653
Повышение цен на данные концерты уже сегодня в 00:00 • Uglystephan — Самара | 21 августа — Нефтекамск | 22 августа • Yanix — Красноярск | 26.09 — Новосибирск | 27.09 🪐 SPACEBOOKING 🪐
custom 53370378464757201654custom 53572906874505915624custom 53076701528908268392
Повышение цен на все концерты — завтра в 00:00 • Успей купить выгоднее!
custom 53370378464757201653custom 53572906874505915622custom 53729170411938288491
Пока ты слушаешь музыку на полную, расклад такой: — Скоро будем добавлять города к туру Yanix (да, мы ебнутые чуваки, забейте) — Понемногу пакуем чемоданы и собираемся с Uglystephan к концу августа с концертами — Общение с Мелсоном выглядит так, как будто ты общаешься с девушкой, которой ты не нравишься — Проанализировали много кандидатур, с кем можно поработать — все готово — Подготовили вам крутые конкурсы, ко…
custom 537291704119382884914custom 535729068745059156212custom 53370378464757201654
Все концерты доступны в Яндекс Афише — КЭШБЕК —
custom 530767015289082683912custom 53729170411938288498custom 53572906874505915626
SPACEBOOKING | NEW — Представляем к вашему вниманию концерт в Архангельске от CODE80 Встретимся с вами в: • Архангельск | 05.09 — Это будет сольный концерт Юры, отдельный от основного тура! Вспомним все его легендарные треки. 🎫 vk.cc/d03PaD
custom 53370378464757201655custom 53572906874505915621custom 53729170411938288491
SPACEBOOKING pinned a photo
Showing the 12 most recent of 28 posts we hold for @spacesbooking. 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.
@spacesbooking edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 11 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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“SPACEBOOKING” (@spacesbooking), 7,534 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/spacesbooking.
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.