Telegram RegisterThe public register of Telegram

Channel

| АРХИВ | 𐌽𐌉ꤍዘᱛ𑀉𐌳Ⴝ 𐌋.ፑ𐌵𐍂𐍅

@NJFuryDB

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

27subscribers

+0 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1004365802782
TypeChannel
Username@NJFuryDB
Created14 July 2026measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/NJFuryDB

Growth

2711 Aug 2026, 00:15 — 27 subscribers11 Aug 2026, 07:31 — 27 subscribers11 Aug 2026, 00:1511 Aug 2026, 07:31
2 measurements taken within a single day. 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 26–28 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 07:3127no change
11 Aug 2026, 00:1527first reading

Engagement

17 posts held, back to 14 July 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.

ERR · 30 days
179.8%
avg views ÷ 27 subscribers
Avg views / post
48.5
15 posts measured
Reaction rate
6.73%
reactions ÷ views · ER floor
Posts in window
17
of 17 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 3 August 2026
Posts held17 (14 July 20263 August 2026)
Views total728
Reactions total49
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Aug 2026, 07:31 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
2
Links
3

Lifetime counters from Telegram’s own channel header, read 11 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.

Reaction mix

49 reactions across 15 posts, in 8 distinct kinds. The most used accounts for 28.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1428.6%
🦄1428.6%
🔥816.3%
💔48.16%
😨48.16%
👍36.12%
❤‍🔥12.04%
🥰12.04%

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 15 of the 17 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 49reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 14 July 2026 to 3 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.

Recent posts

3 Aug 2026, 20:38 UTC31 views10 reactionsread 11 August 2026

Сапп: ребят я в армейку

💔4😨4🦄2

3 Aug 2026, 20:37 UTCviews —

Channel name was changed to «| АРХИВ | 𐌽𐌉ꤍዘᱛ𑀉𐌳Ⴝ 𐌋.ፑ𐌵𐍂𐍅»

3 Aug 2026, 10:41 UTC24 views4 reactionsread 11 August 2026
Forwarded from @agent_Peggy_Carter_DB

Posted without readable text

2❤‍🔥1🦄1

24 Jul 2026, 20:30 UTC65 views3 reactionsread 11 August 2026

—И что, ну, вернулся и пусть будет. Тебе же легче. Ты такую тягу не осилил. Фьюри пожал плечами и встал, медленно обходя стол и останавливаясь рядом с Джоном. Николас опустил свою руку на плечо Уокера и слегка сжал его. —Ты сильный, Джон. Ты справишься. Один, или со мной – без разницы.

1🔥1🦄1

24 Jul 2026, 20:10 UTC59 views3 reactionsread 11 August 2026

—Все нормально, малыш. Выговариваться – дело хорошее. Хорошо, что ты не держишь это в себе. Плохо, что ты никому не доверяешь. Сотрудники Щ.И.Та должны доверять друг другу, а ты этого не делаешь. Как и тебе тут почти никто не доверяет, кроме меня. Ведь я знаю, что ты можешь измениться. Сказал Джозеф, откинувшись на спинку стула и глядя на собеседника, позволив себе лёгкую улыбку.

🔥1🥰1🦄1

24 Jul 2026, 19:57 UTC49 views2 reactionsread 11 August 2026

Николас сидел в кабинете, перебирая какие-то случайные бумаги — отчёты, всякие файлы и тому подобное, как вдруг послышался стук в дверь. Мужчина оторвал взгляд от бумаг и взглянул на дверь. —Что же вас несёт в такой час? Заходите. Пробурчал он, убирая бумаги со стола в ящик, тяжко выдыхая и понимая, что их придется рассмотреть позже.

🔥1🦄1

24 Jul 2026, 17:43 UTC46 views2 reactionsread 11 August 2026

👤: Фьюри, как вам мстители? Тяжело ли с ними работать? Раз вы такие любознательные, что ж... Работать с Мстителями — все равно что пасти котов, только эти коты могут сжечь Нью-Йорк дотла. Каждое утро я молюсь, чтобы хотя бы один из них просто надел костюм по инструкции, но нет — бог, пришелец и солдат с вибраниумом всегда знают лучше. А когда они всё-таки собираются вместе, моя единственная надежда — что они уничтож

1🦄1

22 Jul 2026, 22:14 UTC49 views6 reactionsread 11 August 2026

Понятия не имею, малыш. 🤷‍♂

🔥32🦄1

20 Jul 2026, 18:11 UTC53 views3 reactionsread 11 August 2026
Photo

Гуся в шоке. Я тоже в шоке. Все в шоке. Все любят Гусю.

2🦄1

18 Jul 2026, 11:58 UTC59 views3 reactionsread 11 August 2026

Добрый день. Наконец-то хоть кто-то принял правильное решение. Надеюсь, Уокеру здесь понравится. И ещё одна новость — кажется, у Марии Хилл появился свой блог. Кажется, весь Щ.И.Т решил, что им это необходимо.

1🔥1🦄1

17 Jul 2026, 20:06 UTC60 views3 reactionsread 11 August 2026

—Хм, дай-ка подумать... О, что же это? Ник лёгким движением руки достал из плаща дневник Уокера, листая страницы и усмехаясь. —Прямое доказательство того, что один ты никак не справляешься, Джон. Вообще никак. Поэтому я стою здесь и пытаюсь внедрить в твою голову, что другие тоже могут помочь. У нас хорошие специалисты есть. Он подошёл к Уокеру и отдал ему дневник, похлопав по плечу и начал уходить, но в след брос

1🔥1🦄1

17 Jul 2026, 19:02 UTC48 views1 reactionsread 11 August 2026

—Ну-ну, не обижайся ты. Ты правда наделал дел. Но мне хочется помочь тебе, я знаю, что ты очень себя винишь из-за этого. Николас пожал плечами. —Считай, что я тебя спасаю от тебя же самого. Стань моим агентом, Джон. И, я обещаю, все от тебя отстанут. Ну, может, и не все, но большинство.

1

Showing the 12 most recent of 17 posts we hold for @NJFuryDB. 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 — 592,172 of 1,160,990entries 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.

Forward network

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.

Mentions

Named by 1 registered channel — 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.

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

“| АРХИВ | 𐌽𐌉ꤍዘᱛ𑀉𐌳Ⴝ 𐌋.ፑ𐌵𐍂𐍅” (@NJFuryDB), 27 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/NJFuryDB.

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.