Telegram RegisterThe public register of Telegram

Channel

navedi.

@navedivfx

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

255subscribers

-1 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-1002198312067
TypeChannel
Username@navedivfx
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 8 August 2026
On Telegramt.me/navedivfx

Growth

255256255.57 Aug 2026, 14:22 — 256 subscribers8 Aug 2026, 09:17 — 256 subscribers8 Aug 2026, 14:28 — 255 subscribers7 Aug 2026, 14:228 Aug 2026, 14:28
3 measurements spanning 1 day, net -1. 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 255–256 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 14:28255-1
8 Aug 2026, 09:17256no change
7 Aug 2026, 14:22256first reading

Engagement

17 posts held, back to 3 January 2025the 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 17 posts for this entry, the most recent from 17 May 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 17s
Average length
15s

Measured directly from 5 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

170 reactions across 14 posts, in 4 distinct kinds. The most used accounts for 45.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53552485164007068407745.3%
custom 53549900237939908474224.7%
custom 53552630978146703503520.6%
custom 5355293222715285182169.41%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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 14 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 170reactions 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 3 January 2025 to 17 May 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Telegram Stars

Stars received
2
across the posts below
Posts paid on
1
of 16 we hold a reading for · 6%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @navedivfx. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 17 most recent posts we hold for this entry, published 3 January 2025 to 17 May 2025. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

17 May 2025, 13:02 UTC≈1,670 views34 reactionsread 8 August 2026

Я зимбабвийский долларовый миллионер

custom 535526309781467035016custom 535524851640070684010custom 53549900237939908478

25 Apr 2025, 18:04 UTC≈1,890 views8 reactionsread 8 August 2026

будем на такую тему исполнять

custom 53552485164007068404custom 53549900237939908472custom 53552630978146703502

4 Apr 2025, 19:32 UTC≈2,150 views14 reactionsread 8 August 2026

Press F легенде 🫡

custom 53549900237939908479custom 53552630978146703503custom 53552485164007068402

14 Mar 2025, 09:24 UTC≈2,110 views11 reactionsread 8 August 2026
Forwarded from @daloreeePhoto

Photo, posted without a caption

custom 53549900237939908475custom 53552485164007068403custom 53552932227152851823

23 Feb 2025, 12:27 UTC≈1,550 views17 reactionsread 8 August 2026
Forwarded from @hyprmotionVideo

😎 Монтажники, не щелкайте клювом Мы с коллегами по цеху объединились и собрали для вас особенную подборку полезностей! 💪 Это ваш шанс прокачать насмотренность, набраться вдохновения и залутать вкусные материальчики Что внутри? ⚡️Крутые референсы и разборы работ ⚡️Пресеты, паки и проджекты ⚡️Гайды и фишки от опытных ребят И МНОГОЕ ДРУГОЕ! 🗂 ДОБАВИТЬ 🗂 ДОБАВИТЬ 🗂 ДОБАВИТЬ Сохрани, чтобы не потерять и поделись с др

custom 53552485164007068409custom 53549900237939908474custom 53552630978146703504

18 Feb 2025, 14:49 UTC≈1,390 views3 reactionsread 8 August 2026
Video

Все таки решил дропнуть недоделанный скрап видос вместе с @navedivfx. Ну а на данный момент ведется работа над тремя крутыми проектами, которые вы вскоре увидите 🥸

custom 53552630978146703502custom 53552485164007068401

16 Feb 2025, 16:34 UTC≈1,300 views3 reactionsread 8 August 2026
File

File, posted without a caption

custom 53549900237939908471custom 53552485164007068401custom 53552630978146703501

16 Feb 2025, 16:19 UTC≈1,160 views8 reactionsread 8 August 2026

Не теряйте меня, времени нет немного постить что-то, но скоро надеемся работка будет🤩

custom 53552932227152851825custom 53552630978146703502custom 53549900237939908471

27 Jan 2025, 05:45 UTC≈1,440 views11 reactionsread 8 August 2026
Video

Video, posted without a caption

custom 53552485164007068409custom 53549900237939908472

Showing the 12 most recent of 17 posts we hold for @navedivfx. 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 — 844,775 of 1,176,251entries 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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

“navedi.” (@navedivfx), 255 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/navedivfx.

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.