23 Jun 2026, 08:04 UTC59 viewsread 13 August 2026
Photo
A second before the excellent explosion of the fighters #3_separate_assault_brigade @nazdivision
Channel
Nuremberg
@nazdivision
On this record: Growth · Engagement · Posts · Citations · Cite this entry
3subscribers
+0 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1004494132360 |
|---|---|
| Type | Channel |
| Username | @nazdivision |
| Created | 23 June 2026 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/nazdivision |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 13:08 | 3 | no change |
| 13 Aug 2026, 19:49 | 3 | first reading |
Engagement
4 posts held, back to 23 June 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 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 4 posts for this entry, the most recent from 23 June 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
23 Jun 2026, 08:01 UTC60 viewsread 13 August 2026
Photo
Dead Fighters #12th_Special_forces_brigade_Azov Somewhere in the field @nazdivision
23 Jun 2026, 07:16 UTC54 viewsread 13 August 2026
Photo
N A V I G A T I O N #12th_Special_forces_brigade_Azov #3_separate_assault_brigade #67_separate_mechanized_brigade #24th_separate_assault_battalion_Aidar #Russian_Volunteer_Corps #Kraken @nazdivision
23 Jun 2026, 07:00 UTCviews —
Channel created
Showing the 4 most recent of 4 posts we hold for @nazdivision. 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.
Citation-graph rank
Citation-graph rank — 1,391,226 of 1,581,209entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
“Nuremberg” (@nazdivision), 3 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/nazdivision.
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.