Telegram RegisterThe public register of Telegram

Channel

NEAR Legion

@NEARLegion

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

1,836subscribers

+5 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003143608336
TypeChannel
Username@NEARLegion
CreatedBetween 1 September 2025 and 30 November 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/NEARLegion

Growth

1,8311,8411,8366 August 2026 — 1,831 subscribers6 August 2026 — 1,831 subscribers6 August 2026 — 1,838 subscribers10 August 2026 — 1,841 subscribers12 August 2026 — 1,836 subscribers6 August 202612 August 2026
5 measurements spanning 7 days, net +5. 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,830–1,843 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 22:341,836-5
10 Aug 2026, 02:521,841+3
6 Aug 2026, 18:501,838+7
6 Aug 2026, 06:491,831no change
6 Aug 2026, 03:181,831first reading

Engagement

26 posts held, back to 28 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 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
17.0%
avg views ÷ 1,836 subscribers
Avg views / post
312
26 posts measured
Reaction rate
4.26%
reactions ÷ views · ER floor
Posts in window
26
of 26 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 7 August 2026
Posts held26 (28 July 20267 August 2026)
Views total8,102
Reactions total345
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 17:26 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

Video runtime
2m 51s
Average length
1m 26s

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

265 reactions across 20 posts, in 12 distinct kinds. The most used accounts for 44.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
11744.2%
🔥8331.3%
👎3412.8%
👍155.66%
👏41.51%
💯31.13%
20.755%
😁20.755%
🥰20.755%
💩10.377%
🖕10.377%
🤡10.377%

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

Measured over the 26 most recent posts we hold, published 28 July 2026 to 7 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

7 Aug 2026, 16:39 UTC68 views5 reactionsread 7 August 2026
Photo

🐉 LEGION WEEKLY UPDATE! 📖 Main Discussions 🟢 Self custody vs CEX fight erupts after ColdCard drain scare 🟢 near.com login backup missing passkey failed, chat worried 🟢 HOT protocol quiet again, community split between trust doubt 🟢Open source AI benchmark debate nuance beats raw score 🟢Illia's Sovereign Fund proposal sparks big governance debate week 🗓 Events & News 🟢 Illia's Sovereign Fund proposal was published o

2🔥2💩1

7 Aug 2026, 10:31 UTC225 views42 reactionsread 7 August 2026
Photo

Vanguard rewards are now closed. 🐉 That was only the beginning. The ranks keep rising. Something higher is waking in the dark. Prepare for NEARVANA. All pending rewards for existing Vanguards will be paid out soon.

👎347😁1

7 Aug 2026, 08:21 UTC204 views2 reactionsread 7 August 2026
Video

What happens if you give your password to IronClaw? 🫢 @orange_joe tested it and the results proved why IronClaw is the most secure agent out there. 😇 ➡️Follow Joe for more ironclaw Insights.

2

6 Aug 2026, 18:03 UTC207 views3 reactionsread 7 August 2026
Photo

This week is stacked with IronClaw events globally and virtually. 🐉 🇲🇾 Kuala Lumpur → Aug 7 🇳🇬 Uyo → Aug 7 🌐 Atlas Exchange of Ideas(online)→ Aug 8 🇮🇩 Lampung → Aug 9 🇮🇳 Mumbai → Aug 9 ➡️Join us at an event NEAR you: https://luma.com/ironclaw

3

6 Aug 2026, 13:45 UTC238 views16 reactionsread 7 August 2026

🥁 Announcing the winners for the 1st NEAR Legion Video Content Campaign! We had 40+ submissions with some very creative takes to pitch NEAR AI's Private Chat, a must for your day-to-day interactions with AI. Winners: 🥇 @Lightt007 — 60 NEAR — Video 🥈 @Om7ethh — 45 NEAR — Video 🥉 @Curetor — 25 NEAR — Video Honorary mentions (in no particular order): 🏅 @masumgunda — 10 NEAR — Video 🏅 @sarusensei — 10 NEAR — Video 🏅

12🔥3🤡1

6 Aug 2026, 07:01 UTC221 views13 reactionsread 7 August 2026
Photo

This is what the agentic era looks like in action. 😀 Workshops across 🇮🇳 🇧🇷 🇮🇩 🇪🇨 🇲🇾 🇰🇷 🇺🇸 🇻🇳 — hundreds of builders learning to ship secure agents on IronClaw. ➡️Check out upcoming events here.

🔥84👍1

5 Aug 2026, 12:07 UTC249 views13 reactionsread 7 August 2026
Photo

We are back with another Eco Collab Call. Joining us today are Vlad from Trezu, Armand from Aurora & Stephanie from NF Events team. It's invite-only but open to all Ascendent and above ranked members of the Legion.

6🔥4👍3

5 Aug 2026, 08:21 UTC249 views10 reactionsread 7 August 2026
Photo

When the product holds health information, that becomes a real problem. Using Centralized models means your data is going somewhere. @orange_joe’s approach with NEAR AI + TEEs + smart routing is how you fix it. ➡️Watch how Joe keeps his health data private with NEAR AI

5🔥3👍2

4 Aug 2026, 13:01 UTC355 views15 reactionsread 7 August 2026
Photo

Your feedback shapes Near Builders.🐉 We’re building the best platform for builders on NEAR - open, community-owned, and permissionless by design. Try it out → Share feedback + screenshot in Legion Chat Top entries can win up to 10 $NEAR 🪙 Deadline: Monday 11:59 PM UTC Try it today at nearbuilders.org

9🔥4👍2

4 Aug 2026, 11:36 UTC275 views9 reactionsread 7 August 2026
Photo

New proposal from Illia is live on the NEAR Governance Forum, laying out a vision for a NEAR Sovereign Fund. 💎 The floor is open to validators, House of Stake delegates, and the whole NEAR community. ➡️Read the full post below and weigh in here

6🔥3

4 Aug 2026, 06:54 UTC287 views7 reactionsread 7 August 2026
Video

The simplest path to a user-owned agent: Sign in → Stake NEAR → Activate Agent 😄 Your private IronClaw instance is ready. 🫢 Your agent. Your keys. Your data.

7

3 Aug 2026, 13:08 UTC307 views27 reactionsread 7 August 2026
Photo

NEAR Intents is the fastest-growing cross-chain infrastructure. 👀 ➡️ Read Near Intent’s July Breakdown

🔥1472👏2🖕1🥰1

Showing the 12 most recent of 26 posts we hold for @NEARLegion. 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 — 17,955 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

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 4 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.

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

“NEAR Legion” (@NEARLegion), 1,836 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/NEARLegion.

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.