Здесь пишу ИСКЛЮЧИТЕЛЬНО своё мнение.
Для связи - [email protected]
Бот для связи только по координатам - @Rus_ni_peace_da_bot
Сообщить о воздушной цели - @Yug_mopedi_bot
Я НИКОГДА НЕ ПИШУ ВАМ В ЛИЧКУ В ТЕЛЕГРАМЕ
Created
17 April 2022 — measured — dated from the channel’s first post
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 8 August 2026 and assigned it the closest of 31 fixed categories, at 47% 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 word for word on 1 other registered channel. They sit inside a group of 377 channels that share the same post bodies with each other. 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 (4 of the pairs behind the counts below)
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. None of the 5 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 17,270 comparable posts for this entry, running 17 April 2022 to 8 August 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).
Across the whole group of 377, the earliest publisher we hold is @mash. That is a statement about our reading window, not a claim of authorship.
Views and reactions moved apart
On 19 of the 259 posts we watched over 30 days, the view counter climbed while the reaction counter stayed where it was — by more than this channel’s own reactions-per-view rate can account for. That rate, measured on this entry, is 0.0116 reactions per view.
Each interval, as we read it — views and reactions before and after
Expected is the view gain multiplied by this channel’s own prior reactions-per-view rate over the same post — not a corpus average, so a channel whose audience never reacts is compared only against itself. Every interval is credited in the direction that makes the observation harder to record, never easier: t.me renders views and reactions to three significant figures above ~1,000, so a raw delta can be a rendering step. Every delta below is at least 4 x the coarser reading's step, the view gain is discounted by a full step and the reaction gain credited with one. Measured by tgregister velocity.py (our own t.me/s/ readings).
What this does and does not say. It says the two counters moved apart, by more than rounding and more than this channel’s own history predicts. It asserts no cause. Views arriving from outside Telegram, an embedded or forwarded copy of the post, and a burst of readers who simply do not react all produce this shape. This detector has recorded very few observations across the whole register, and its precision has not been measured; treat it as an anomaly worth looking at, not as a finding.
Recorded under the keys clone_mutual · view_reaction_decoupling, last confirmed 7 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.
Also posting the same content
This channel’s posts match, word for word or near enough, posts on 376 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
326 more channels are in this same group but not listed individually here.
Growth
62 measurements spanning 93 days, net -90,519. 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 2,568,817–2,686,492 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 62
Measured (UTC)
Subscribers
Change
6 Nov 2026, 14:39
2,582,395
-1,083
5 Nov 2026, 12:57
2,583,478
-1,391
4 Nov 2026, 14:36
2,584,869
-818
3 Nov 2026, 17:07
2,585,687
+1,684
2 Nov 2026, 16:01
2,584,003
+933
1 Nov 2026, 16:48
2,583,070
-209
31 Oct 2026, 17:56
2,583,279
-1,027
30 Oct 2026, 16:01
2,584,306
-1,302
29 Oct 2026, 12:46
2,585,608
-1,044
28 Oct 2026, 09:09
2,586,652
-594
27 Oct 2026, 09:49
2,587,246
-1,293
26 Oct 2026, 11:48
2,588,539
-1,231
25 Oct 2026, 13:04
2,589,770
-1,028
24 Oct 2026, 13:20
2,590,798
-1,192
23 Oct 2026, 11:11
2,591,990
-1,747
22 Oct 2026, 08:56
2,593,737
-1,776
21 Oct 2026, 04:01
2,595,513
-1,611
20 Oct 2026, 04:27
2,597,124
-1,778
19 Oct 2026, 01:28
2,598,902
-747
17 Oct 2026, 23:10
2,599,649
first reading
Engagement
40,698 posts held, back to 17 April 2022 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 6,135 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
36.6%
avg views ÷ 2,582,395 subscribers
Avg views / post
944,000
259 posts measured
Reaction rate
1.51%
reactions ÷ views · ER floor
Posts in window
259
of 40,698 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
Window
Rolling 30 days · latest post in window 7 November 2026
Posts held
40,698 (17 April 2022 – 7 November 2026)
Views total
244,540,000
Reactions total
3,692,989
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Nov 2026, 05:30 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
≈5,470
Videos
≈3,120
Links
≈1,860
Lifetime counters from Telegram’s own channel header, read 7 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
1h 10m
Average length
1m 51s
Measured directly from 38 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.
View velocity
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
Computed from 259 of this channel’s own posts over the last 30 days (1 of the 24-hour readings behind this are interpolated, not measured directly): across 222 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 2.7 hours of being posted; a typical post has already reached 41.0% of its 24-hour view count within the first hour, and 75.7% within the first six; the median 24-hour reach across those posts is 786,500 views — 30.5% of this channel’s own subscriber count (90th percentile 1,020,000).
8 most recently posted, with a view-velocity reading
60 minutes: 302,000 → 3.0 hours: 379,486 interp. → 6.0 hours: 482,000still climbing at last reading
not yet at 24h
40 minutesprovisional — final view count still climbing
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
Reaction mix
10,143,538 reactions across 1,000 posts, in 14 distinct kinds. The most used accounts for 44.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🙏
4,490,255
44.3%
🤬
2,756,264
27.2%
❤
895,287
8.83%
🔥
824,590
8.13%
😢
337,901
3.33%
👍
322,370
3.18%
😁
211,620
2.09%
🤣
132,036
1.30%
😡
66,383
0.654%
👀
49,312
0.486%
🤷
24,083
0.237%
❤🔥
14,094
0.139%
🫡
10,127
0.1%
🥰
9,216
0.091%
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,000 of the 1,000 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 10,143,538 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 27 August 2026 to 7 November 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
Telegram’s own ‘edited’ marker: 4 of 259 posts held from the last 30 days (1.54%) 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).
2 ракеты по Наливайковке
4 ракеты по Киеву
2 ракеты по Обухову
🙏3,290🤬2,550😢251❤151😡150❤🔥22
Showing the 12 most recent of 40,698 posts we hold for @vanek_nikolaev. 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.
Posts edited after publishing
@vanek_nikolaev 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.
First edit seen
30 August 2026
Most recent edit
30 August 2026
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republished by 99 registered channels. The 48 listed are the ones that have forwarded the most posts; the rest are counted here but not each listed.
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
Named by 63 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
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.
Handles this channel named that no longer answer
Dead references
23
handles named in this channel’s posts, vacant today
Evidenced gone
2
we ourselves saw one of these resolve, at some point
Never seen alive
21
vacant every time we have ever looked
@vanek_nikolaev named 23 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
@snihyrivkachannel named in 2 posts, 8 August 2026 – 8 August 2026 · confirmed gone 6 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@pentagonkh named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 13 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@peace_da_rus_ni_bot named in 48 posts, 8 August 2026 – 8 August 2026
@army_14reg named in 13 posts, 8 August 2026 – 8 August 2026
@moped_yug_bot named in 9 posts, 8 August 2026 – 8 August 2026
@kraken_kha named in 6 posts, 8 August 2026 – 8 August 2026
@guns148 named in 4 posts, 8 August 2026 – 8 August 2026
@ii_mechanized_battalion_zsu named in 4 posts, 8 August 2026 – 8 August 2026
@non_fake_ks named in 3 posts, 8 August 2026 – 8 August 2026
@shturmovarota3 named in 2 posts, 8 August 2026 – 8 August 2026
@rmglvya named in 1 post, 8 August 2026 – 8 August 2026
@sinnitsa named in 1 post, 8 August 2026 – 8 August 2026
@skylordss named in 1 post, 8 August 2026 – 8 August 2026
@azovangels named in 1 post, 8 August 2026 – 8 August 2026
@this_is_war88 named in 1 post, 8 August 2026 – 8 August 2026
@this_is_war_ab3 named in 1 post, 8 August 2026 – 8 August 2026
@vicious_artillery named in 1 post, 8 August 2026 – 8 August 2026
@whirli_geek named in 1 post, 8 August 2026 – 8 August 2026
@martivkyy_kit named in 1 post, 8 August 2026 – 8 August 2026
@mykolaiv_d named in 1 post, 8 August 2026 – 8 August 2026
@fenririam named in 1 post, 8 August 2026 – 8 August 2026
@perun_group named in 1 post, 8 August 2026 – 8 August 2026
@recrut_46 named in 1 post, 8 August 2026 – 8 August 2026
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.
Повістки Київ / Повестки Киев @kyiv_povestka · 227,492#83
Головне управління розвідки МО України @DIUkraine · 221,395#84
Read from Telegram’s recommendation API, most recently 7 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.
#SK# говорить🇺🇦 @SK_DM_SK · 192,077 Telegram ranks this channel #1 of 89 here — alongside 88 others — read 14 August 2026
БЕЗПЕЧНИЙ РЕГІОН @bezpechniyregion · 163,868 Telegram ranks this channel #1 of 79 here — alongside 78 others — read 12 August 2026
monitor @war_monitor · 959,985 Telegram ranks this channel #1 of 87 here — alongside 86 others — read 8 August 2026
Підслухано в поліції @podslyshenopolice · 19,328 Telegram ranks this channel #2 of 79 here — alongside 78 others — read 1 October 2026
Північний Сич 🦉 @Northern_Sich_ukr · 109,143 Telegram ranks this channel #2 of 85 here — alongside 84 others — read 16 August 2026
Повітряна тривога 🚀 @air_alert_telegram · 100,944 Telegram ranks this channel #2 of 87 here — alongside 86 others — read 15 August 2026
UA HiMARS 18+🫡 @war_ua_22 · 19,432 Telegram ranks this channel #3 of 80 here — alongside 79 others — read 3 October 2026
🚀 РАКЕТНА неБЕЗПЕКА 🚀 @rocket_danger_lviv · 399,153 Telegram ranks this channel #3 of 82 here — alongside 81 others — read 10 August 2026
monitoring захід @monitoring_zaxid · 161,063 Telegram ranks this channel #4 of 77 here — alongside 76 others — read 23 August 2026
Типичная Украина — Новости Киев,Київ @tipichna_ukraine · 202,932 Telegram ranks this channel #4 of 84 here — alongside 83 others — read 11 August 2026
Правда Васильків 🇺🇦 @Vasylkiv_Vasilkov · 24,183 Telegram ranks this channel #5 of 75 here — alongside 74 others — read 18 September 2026
срач в хаті 2.0 @srachvhati2 · 23,646 Telegram ranks this channel #5 of 56 here — alongside 55 others — read 18 September 2026
Беларускі Гаюн | Belarusian Hajun project @Hajun_BY · 222,693 Telegram ranks this channel #5 of 87 here — alongside 86 others — read 11 August 2026
Повестки в Киеве @agendaKyiv · 155,104 Telegram ranks this channel #6 of 87 here — alongside 86 others — read 15 August 2026
KIEVAVTO @kievavto2 · 65,221 Telegram ranks this channel #7 of 61 here — alongside 60 others — read 24 August 2026
Укрзалізниця @UkrzalInfo · 237,811 Telegram ranks this channel #7 of 90 here — alongside 89 others — read 11 August 2026
6666 @alkhim6666 · 148,471 Telegram ranks this channel #8 of 50 here — alongside 49 others — read 11 September 2026
Бро скинув мем @bromeeems · 311,555 Telegram ranks this channel #8 of 82 here — alongside 81 others — read 10 August 2026
Exilenova+ @exilenova_plus · 323,205 Telegram ranks this channel #9 of 74 here — alongside 73 others — read 11 August 2026
Сергій FLASH | Про технології @serhii_flash · 171,710 Telegram ranks this channel #11 of 81 here — alongside 80 others — read 12 August 2026
Тарас Юрист Адвокат Одесса @TarasOdessa · 141,919 Telegram ranks this channel #13 of 89 here — alongside 88 others — read 13 August 2026
ҐЄЇ @ukrainiatrash · 25,736 Telegram ranks this channel #14 of 69 here — alongside 68 others — read 12 September 2026
Arestovich / Official @O_Arestovich_official · 236,677 Telegram ranks this channel #14 of 93 here — alongside 92 others — read 11 August 2026
Mister.Biznes @biznesuha · 295 Telegram ranks this channel #15 of 87 here — alongside 86 others — read 11 August 2026
This channel appears in 572 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Domains linked from posts
79 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.
Wikipedia
3 Wikipedia articles name this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.
Skadovsk(en.wikipedia.org) “…of 2025, the city is occupied by [[Russia]].{{Cite web |url=https://t.me/vanek_nikolaev/18378 |title=тем временем кацапы продолжают минировать...…” read 1 November 2026
Авіаудар по Новій Каховці 15 вересня 2023(uk.wikipedia.org) “…|Дата = 15 вересня 2023
|Час = ~9:22 ([[UTC+2]]){{cite web|url=https://t.me/vanek_nikolaev/17717|title=Николаевский Ванёк|language=uk|date=2023-09-15}}…” read 1 November 2026
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 6 November 2026 — this
entry's latest reading, not the date you are reading this.
“Николаевский Ванёк” (@vanek_nikolaev), 2,582,395 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/vanek_nikolaev.
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.
