Telegram RegisterThe public register of Telegram
Telegram profile photo for Новини Ніжина

Channel

Новини Ніжина

@robofsdad

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

2subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003606657882
TypeChannel
Username@robofsdad
DescriptionАзаза
CreatedBetween 1 December 2025 and 3 February 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live14 August 2026
Measurements held2
On Telegramt.me/robofsdad

Growth

27 August 2026 — 2 subscribers14 August 2026 — 2 subscribers7 August 202614 August 2026
2 measurements spanning 6 days. 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 1–3 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 03:192no change
7 Aug 2026, 18:482first reading

Engagement

20 posts held, back to 3 February 2026the 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 14 May 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
20
Videos
11
Links
18

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.

Video runtime
33s
Average length
17s

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.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏1100.0%

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 1 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 1reactions 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 3 February 2026 to 14 May 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.

Recent posts

14 May 2026, 16:32 UTCviews —

The owner of this channel has been inactive for the last 1 month. If they remain inactive for the next 10 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

6 Apr 2026, 14:38 UTC16 viewsread 14 August 2026
Video

Video, posted without a caption

Signed 𝔗𝔯𝔬𝔣𝔨𝔞𝔞 Ptashka

13 Mar 2026, 20:48 UTC35 viewsread 14 August 2026
Forwarded from @airAlarm_Kyiv

3 борти Ту-95МС з аеродрому «Бєлая» прямують західним курсом. ⠀ Якщо виліт бойовий, вихід на пускові рубежі очікується близько 02:00.

13 Mar 2026, 19:57 UTC34 viewsread 14 August 2026

❗️ Ймовірно, на сьогодні запланована ракетна атака атака ворога! За наявною інформацією, противник може готувати комбінований ракетно-дроновий удар. 🔻 Ймовірні засоби ураження: ✈️ Авіація: • 6× бортів Ту-22М3 • 6× бортів МіГ-31К/И 🚀 Ракетне озброєння: • 6× аеробалістичних ракет “Кинжал” • 4× гіперзвукових ракет “Циркон” • 30× балістичних ракет “Искандер-М” • 10× крилатих ракет “Искандер-К” • 6х ракет Х-22/Х-32 🚢

18 Feb 2026, 14:09 UTC28 viewsread 14 August 2026
Forwarded from @taktychna_rukavuchkaa

❗️За попередньою інформацією, по Ніжину було застосовано балістичні ракети з касетною бойовою частиною!

14 Feb 2026, 16:52 UTC25 viewsread 14 August 2026

❗️Значна загроза пусків БРСД «Орєшніка» з полігону «Капустин Яр» зберігається до 19.02. У звʼязку з цим може бути значно більше тривог. Приєднатися | WARSHAL

14 Feb 2026, 13:51 UTC21 viewsread 14 August 2026
Forwarded from @eRadarrua

❗️ У найближчі дні, Вам почнуть розказувати про супер-мега-пупер масований обстріл, із застосування 250 ракет і 1000 БпЛА на 24 лютого. Не ведіться. росія ніколи не привʼязується до конкретних дат.

13 Feb 2026, 19:28 UTC20 viewsread 14 August 2026
Forwarded from @nizhyninfo_official

🚀 Вибухи в районі Ніжина: повідомляють про дві ракети 💥 Сьогодні в районі міста Ніжин пролунали вибухи. За попередньою інформацією, йдеться про дві ракети. ℹ️ Інформація доповнюється. 

13 Feb 2026, 12:00 UTC22 viewsread 14 August 2026

Я сьогодні загинув, мамо.... Під Херсоном, у важкому бою. Мені більш не печуть мої рани, Я тепер біля Бога стою. Попрошу я тебе, моя рідна, Не туди, і за мною не плач.

Showing the 12 most recent of 20 posts we hold for @robofsdad. 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.

Mentions

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.

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

“Новини Ніжина” (@robofsdad), 2 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/robofsdad.

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.