Telegram RegisterThe public register of Telegram
Telegram profile photo for Бабуся Світуся

Channel

Бабуся Світуся

@babusya_svitusya

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry

54,308subscribers

-389 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001528530540
TypeChannel
Username@babusya_svitusya
DescriptionАГРЕГАТОРИ НОВИН🇺🇦 Волонтер Всеукраїнського жіночого руху «За вільну Україну» Написати мені - @canal_babusya Ютуб: https://youtube.com/@babusya_svitusya Інстаграм: https://instagram.com/babusya_svitusya?igshid
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/babusya_svitusya

Topic

National news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 21 August 2026 and assigned it the closest of 31 fixed categories, at 57% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 12 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@kudy_letyt/11394010 Aug 2026, 12:33 UTC@babusya_svitusya/365781 · this entry10 Aug 2026, 12:34 UTC1.00under a minute
@kudy_letyt/1168203 Sept 2026, 15:31 UTC@babusya_svitusya/373155 · this entry3 Sept 2026, 15:34 UTC1.004 minutes
@kudy_letyt/11927526 Sept 2026, 20:20 UTC@babusya_svitusya/380431 · this entry26 Sept 2026, 20:21 UTC1.0072 seconds
@kudy_letyt/1205962 Oct 2026, 18:55 UTC@babusya_svitusya/382922 · this entry2 Oct 2026, 18:56 UTC1.00under a minute
@kudy_letyt/12620821 Oct 2026, 20:09 UTC@babusya_svitusya/389056 · this entry21 Oct 2026, 20:12 UTC0.983 minutes
@kudy_letyt/11904025 Sept 2026, 02:55 UTC@babusya_svitusya/379887 · this entry25 Sept 2026, 02:59 UTC0.964 minutes
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@kudy_letyt32 (6/8 hand-verifiable sample passed)0.996 days@kudy_letyt (31–1)
@raketa_trevoga19 (8/8 hand-verifiable sample passed)0.952.4 hours@raketa_trevoga (19–0)
@Tsaplienko17 (8/8 hand-verifiable sample passed)1.007 minutes@Tsaplienko (13–4)
@uanova14 (8/8 hand-verifiable sample passed)0.948 minutes@uanova (10–4)
@Bratchuk_Sergey13 (8/8 hand-verifiable sample passed)1.007 minutes@Bratchuk_Sergey (9–4)
@smolii_ukraine12 (8/8 hand-verifiable sample passed)0.992 minutes@smolii_ukraine (11–1)
@u_now11 (8/8 hand-verifiable sample passed)0.9572 seconds@u_now (11–0)
@ukraine_pyxx10 (8/8 hand-verifiable sample passed)1.00under a minute@ukraine_pyxx (9–1)
@de_raketaua10 (8/8 hand-verifiable sample passed)1.001.8 hours@de_raketaua (8–2)
@ppy_radar_ukr10 (8/8 hand-verifiable sample passed)0.99under a minute@ppy_radar_ukr (7–3)
@uaobozrevatel10 (8/8 hand-verifiable sample passed)1.0065 minutes@uaobozrevatel (10–0)
@PpoUaRadar09 (8/8 hand-verifiable sample passed)1.0072 seconds@PpoUaRadar0 (8–1)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 236 of the 236 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 1,453 comparable posts for this entry, running 7 August 2026 to 16 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 17 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

54,30855,72055,0147 August 202615 November 2026
65 measurements spanning 100 days, net -389. 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 54,096–55,932 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
15 Nov 2026, 06:1054,308-132
11 Nov 2026, 22:4454,440-51
10 Nov 2026, 03:0054,491-43
8 Nov 2026, 17:0654,534-51
7 Nov 2026, 10:0754,585-58
6 Nov 2026, 07:2854,643-63
5 Nov 2026, 06:5554,706-42
4 Nov 2026, 04:5054,748-71
3 Nov 2026, 01:3754,819+45
2 Nov 2026, 01:3154,774+159
1 Nov 2026, 00:2854,615-51
30 Oct 2026, 22:3554,666+14
30 Oct 2026, 00:0054,652-43
28 Oct 2026, 23:5654,695-32
28 Oct 2026, 00:2754,727-31
27 Oct 2026, 00:0454,758+3
26 Oct 2026, 01:4754,755-32
25 Oct 2026, 04:0654,787-53
24 Oct 2026, 06:4054,840-38
23 Oct 2026, 09:1654,878first reading

Engagement

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

ERR · 30 days
7.31%
avg views ÷ 54,308 subscribers
Avg views / post
3,970
1,104 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
1,106
of 3,815 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 16 November 2026
Posts held3,815 (7 August 2026 – 16 November 2026)
Views total4,381,597
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 23:35 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
≈80,900
Videos
≈40,100
Links
≈11,400

Lifetime counters from Telegram’s own channel header, read 16 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
29m 53s
Average length
34s

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

Recent posts

Telegram’s own ‘edited’ marker: 88 of 1,106 posts held from the last 30 days (7.96%) 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).

16 Nov 2026, 23:32 UTC305 viewsread 16 November 2026
Video

Кримський міст аж погнуло

Signed Світуся Телеграм: Бабуся Світуся

16 Nov 2026, 23:16 UTC≈1,790 viewsread 16 November 2026
Photo

Двіжуха

Signed Світуся Телеграм: Бабуся Світуся

16 Nov 2026, 23:15 UTC≈1,850 viewsread 16 November 2026

Сумщина 1 БпЛА на Суми Чернігівщина 1 БпЛА на Городню 10 БпЛА на Михайло-Коцюбинське 1 БпЛА на Носівку Житомирщина 5 БпЛА з Білорусі на Овруч Київщина 1 БпЛА на Припʼять 1 реактивний БпЛА на Переяслав Дніпропетровщина 1 БпЛА на Шахтарське 1 реактивний БпЛА на Лихівку

Signed Світуся Телеграм: Бабуся Світуся

16 Nov 2026, 23:04 UTC≈2,250 viewsread 16 November 2026

Чернігівщина: БПЛА на Городню; Славутич — 7х; Олишівку. Київщина: БПЛА на Чорнобиль — 3х; Припʼять — 2х; Згурівку (реакт.). Дніпропетровщина: БПЛА на Перещепине (реакт.).

Signed Tetianka

16 Nov 2026, 23:01 UTC≈2,360 viewsread 16 November 2026
Video

Момент прильоту по Кримському мосту

Signed Tetianka

16 Nov 2026, 22:59 UTC≈2,350 viewsread 16 November 2026

Загалом вже десь 30 БПЛА від Чернігівщини до ЧЗВ ланцюг БПЛА.

Signed Tetianka

16 Nov 2026, 22:55 UTC≈2,700 viewsread 16 November 2026

Вишгородський район - масована або ракетна загроза.

Signed Світуся Телеграм: Бабуся Світуся

16 Nov 2026, 22:46 UTC≈3,110 viewsread 16 November 2026

Чернігівщина 1 реактивний БпЛА з Сумщини на Короп 3 БпЛА на Городню 6 БпЛА на Славутич Київщина 5 БпЛА на Чорнобиль 1 БпЛА на Припʼять Харківщина 1 реактивний БпЛА на Введенку Дніпропетровщина 1 реактивний БпЛА на Магдалинівку

Signed Світуся Телеграм: Бабуся Світуся

16 Nov 2026, 22:45 UTC≈2,940 viewsread 16 November 2026

Запоріжжя: реактивний БпЛА курсом на місто

Signed Світуся Телеграм: Бабуся Світуся

16 Nov 2026, 22:40 UTC≈3,810 viewsread 16 November 2026
Video

15 влучань в путінський міст

Signed Світуся Телеграм: Бабуся Світуся

16 Nov 2026, 22:39 UTC≈3,600 viewsread 16 November 2026

Відбій по балістиці Відпочивайте, рідненьки

Signed Світуся Телеграм: Бабуся Світуся

16 Nov 2026, 22:39 UTC≈3,630 viewsread 16 November 2026
Photo

Кримський міст зараз

Signed Tetianka

Showing the 12 most recent of 3,815 posts we hold for @babusya_svitusya. 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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

Реальний Київ | Украина
@kievreal1 · 1,550,018
#1
Київ ІНФО | Новини Україна 🇺🇦
@kievinfo_kyiv · 1,261,551
#2
Лачен пише
@lachentyt · 1,576,100
#3
Повітряні Сили ЗС України / Air Force of the Armed Forces of Ukraine
@kpszsu · 938,428
#4
Карта повітряних тривог 🇺🇦
@alarmua · 940,548
#5
monitor
@war_monitor · 958,023
#6
Труха⚡️Україна
@truexanewsua · 3,165,345
#7
Дніпро Alerts 🚀 🚨
@dnipro_alerts · 809,443
#8
INSIDER UA | Україна | Новини
@insiderukr · 2,141,667
#9
Труха⚡️Київ
@truexakyiv · 972,266
#10
Вмикач Київ | Світло💡
@kiev_svet · 235,748
#11
Чому тривога | Радар
@raketa_trevoga · 471,573
#12
Киевский Движ
@k_dvizh · 470,624
#13
Реальна Війна | Україна | Новини
@voynareal · 1,541,547
#14
Левый Берег Киев
@kiev_levyy_bereg · 492,701
#15
🔊⚠️єРадар | Повітряна тривога | Ракетна небезпека
@eRadarrua · 410,667
#16
Куди летить? | Тривога
@radar_raketaa · 490,712
#17
Карта повітряних тривог ‼️ Вибухи ‼️ Ракети ‼️
@povitryanatrivogaaa · 728,432
#18
Київський купол | Графіки
@nebo_raketa · 542,733
#19
Україна Online: Новини | Політика
@UaOnlii · 1,536,697
#20
УС: Україна, новини, політика, війна
@u_now · 1,403,118
#21
Тотальна Зрада
@totallzrada · 265,783
#22
НУ І ДНІПРО! 🇺🇦
@ny_i_dnipro · 289,947
#23
Андрій Смолій
@smolii_ukraine · 523,723
#24
ХДніпро 🇺🇦
@hyevuy_dnepr · 520,852
#25
ТСН новини / ТСН.ua
@tch_channel · 729,418
#26
Тривога України | Радар
@kiev_nebo · 539,280
#27
Бавовна
@ukrbavovna · 800,178
#28
Strategic Control
@strategicontrol · 27,117
#29
Вибухи та бавовна
@vybuhy_bavovna · 82,077
#30
єСвітло💡Київ | Світло
@esvitlo_kyiv_ua · 167,857
#31
Новости Одесса | Одеса
@our_odessa · 436,921
#32
#SK# говорить🇺🇦
@SK_DM_SK · 191,904
#33
Волхва України Ольга Берлінська
@VolxvaUkrain · 166,212
#34
Правий Берег Київ | Киев
@kiev_pravyy_bereg · 181,285
#35
monitoring
@monitorwarr · 85,150
#36
ППО радар | Напрямок ракет | Напрямок шахедів |
@mon1tor_ua · 263,748
#37
🟢 Київ Новини | Live 24/7
@kyiv_novyny_24 · 237,542
#38
ОДЕССА ИНФО LIVE - радар Одеса
@odessa_inform · 375,203
#39
✈️Стратегічна авіація
@StrategicaviationT · 132,886
#40
Захід Головне
@zahid_golovne_ua · 609,899
#41
ОПЕРАТИВНИЙ ІНФОРМ
@operinform · 135,692
#42
БЕЗПЕЧНИЙ РЕГІОН
@bezpechniyregion · 163,283
#43
Де Ракета ?🚀 | Моніторинг
@deraketaua · 154,826
#44
∆✙🍒Гнила черешня🇺🇦✙∆
@gnilayachereha · 412,798
#45
🚀 Ракетна небезпека | України | шахеди | вибухи |
@vibuxaviasia · 56,554
#46
Україна 24/7 - новини
@ukraina_novosti · 1,367,697 (as read 29 August 2026)
#47
КМДА – офіційний канал
@KyivCityOfficial · 403,692
#48
Телеграмна служба новин - Україна
@tgsn_ua · 1,108,673
#49
Ринда моніторить
@kudy_letyt · 159,456
#50
🔊Чому тривога?🚨| Повітряна тривога | Ракетна небезпека | єРадар |
@tryvoga_chomu · 271,891
#51
Повітряна тривога Київ △
@airAlarm_Kyiv · 88,493
#52
Хмельницький LIVE
@khmlv · 298,996
#53
LOS SOLOMAS . КИЇВ
@lossolomas_kyiv · 81,321
#54
Український | ППОшник
@ukrainsiyppohnik · 10,627
#55
osint.air monitor
@osintairmonitor · 4,625
#56
ЦАПЛІЄНКО_UKRAINE FIGHTS
@Tsaplienko · 319,669
#57
🚀 РАКЕТА UA | Тривога України
@war_raketaua · 85,686
#58
Kyiv Alerts 🚀 🚨
@kyiv_alerts · 48,942
#59
Повітряний простір України 🇺🇦
@monikppy · 228,243
#60
Tracking
@the_first_online · 8,054
#61
НУ І НОВІК
@ny_i_novik · 20,902
#62
UA HiMARS 18+🫡
@war_ua_22 · 19,436
#63
Правый Берег Киева
@praviy_bereg_kiev · 141,028
#64
Включатель Днепр⚡️
@vklyuchatel_dnepr_svet · 197,131
#65
УКРАЇНА НАЖИВО 🇺🇦
@UaNazhyvo · 58,675
#66
ППО UA | РАДАР📡
@PpoUaRadar0 · 35,757
#67
НУ І КРИВИЙ РІГ
@ny_i_kryvyi_rih · 9,443
#68
Труха⚡️Дніпро | Новини
@truexadnepr · 399,271
#69
НУ І ПАВЛОГРАД 🇺🇦
@ny_i_pavlograd · 12,775
#70
Одесса INFO ⚓️ 🇺🇦 Новости | Одеса
@odessa_infonews · 989,908
#71
Хуевая Одесса
@xydessa · 943,764
#72
STERNENKO
@ssternenko · 879,121
#73
✙ 🔼Вертикаль
@vert2026 · 113,508
#74
Київ News | Світло
@svitlo_kiyv · 150,647
#75
✙ Київ Оперативний | Kyiv Operative ✙
@kyivoperat · 338,101
#76
Батальйон Монако
@batalionmonako · 982
#77
IMPULSE
@Impulse_011 · 57,541
#78
Скринька Пандори
@pandoras_box_ua · 157,764
#79
Що в повітрі? | Моніторинг
@monitoringwarua · 12,202
#80
Бахмутський Демон 👹
@bahshiddemon · 169,645
#81
єРадіоефір
@air_radioefir · 1,425
#82

Read from Telegram’s recommendation API, most recently 29 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

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.

Миргород ЩДК?
@mirgorodlive · 26,131
Telegram ranks this channel #23 of 70 here — alongside 69 others — read 15 September 2026
Mirgorodtown
@myrhorodtown · 20,421
Telegram ranks this channel #57 of 76 here — alongside 75 others — read 2 October 2026
НУ І НОВІК
@ny_i_novik · 20,902
Telegram ranks this channel #62 of 78 here — alongside 77 others — read 30 September 2026
Черкаси ⚡️Новини
@cherkasy_news_insider · 41,501
Telegram ranks this channel #63 of 82 here — alongside 81 others — read 29 August 2026
The best of Zhytomyr || Війна в Україні || Серйозна група || Житомир
@zhyto_best · 36,631
Telegram ranks this channel #64 of 72 here — alongside 71 others — read 9 September 2026

This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Бабуся Світуся” (@babusya_svitusya), 54,308 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/babusya_svitusya.

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.