Telegram RegisterThe public register of Telegram

Channel

OnePlus Nord 2 | Updates

@OnePlusNord2Updates

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

967subscribers

+0 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-1001481407556
TypeChannel
Username@OnePlusNord2Updates
DescriptionAll about OnePlus Nord 2 ROMs, Kernels, Guides, Mods, NEWS, everything. Official Group :- @OnePlusNord2GlobalOfficial Photography - @Oneplusnord2Gcam Off-Topic - @oneplusnord2offtopic
CreatedBetween 1 April 2019 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/OnePlusNord2Updates

Topic

Technology — 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 11 August 2026 and assigned it the closest of 31 fixed categories, at 98% 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 why it has no browse page of its own yet.

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. 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 (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@OnePlusNord2Updates/197 · this entry7 May 2026, 17:28 UTC@RealmeX7MaxUpdates/5237 May 2026, 17:28 UTC1.00under a minute
@RealmeX7MaxUpdates/52511 May 2026, 06:30 UTC@OnePlusNord2Updates/198 · this entry11 May 2026, 06:31 UTC1.0072 seconds
@RealmeX7MaxUpdates/52826 May 2026, 14:45 UTC@OnePlusNord2Updates/199 · this entry26 May 2026, 14:46 UTC1.00under a minute
@RealmeX7MaxUpdates/5327 Jun 2026, 12:11 UTC@OnePlusNord2Updates/201 · this entry7 Jun 2026, 12:11 UTC1.00under a minute
@RealmeX7MaxUpdates/53610 Jun 2026, 18:06 UTC@OnePlusNord2Updates/204 · this entry10 Jun 2026, 18:06 UTC1.00under a minute
@RealmeX7MaxUpdates/53831 Jul 2026, 14:30 UTC@OnePlusNord2Updates/205 · this entry31 Jul 2026, 14:30 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@RealmeX7MaxUpdates9 (8/8 hand-verifiable sample passed)1.00under a minute@RealmeX7MaxUpdates (81)

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 8 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 20 comparable posts for this entry, running 4 May 2025 to 3 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 2, the earliest publisher we hold is @OnePlusNord2Updates — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 8 August 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 1 other registered channel, 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.

Growth

9677 Aug 2026, 22:49 — 967 subscribers8 Aug 2026, 00:47 — 967 subscribers7 Aug 2026, 22:498 Aug 2026, 00:47
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 966–968 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 00:47967no change
7 Aug 2026, 22:49967first reading

Engagement

20 posts held, back to 4 May 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.

ERR · 30 days
25.3%
avg views ÷ 967 subscribers
Avg views / post
245
3 posts measured
Reaction rate
3.13%
reactions ÷ views · ER floor
Posts in window
3
of 20 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 held20 (4 May 20253 August 2026)
Views total734
Reactions total23
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 00:47 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
127
Videos
4
Links
100

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

205 reactions across 20 posts, in 10 distinct kinds. The most used accounts for 47.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
9847.8%
🔥7737.6%
👍157.32%
🥰52.44%
👏41.95%
😁20.976%
🏆10.488%
👌10.488%
🕊10.488%
😍10.488%

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

Measured over the 20 most recent posts we hold, published 4 May 2025 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, 11:17 UTC204 views5 reactionsread 8 August 2026
Photo

#LunarisAOSP #OFFICIAL #ROM #op6893 LunarisAOSP 3.10 | OFFICIAL | OnePlus Nord 2 | Realme X7 Max | Realme GT Neo By Rakhshan Build type: Gapps Release date: 03-08-2026 ▪️Download ▪️Changelogs | Device ▪️Support Join: @lunaris_hub Follow: @lunaris_update

🔥5

Signed Himanshu R Tyagi

3 Aug 2026, 02:09 UTC232 views9 reactionsread 8 August 2026
Photo

#InfinityX #B #UNOFFICIAL #op6893 InfinityX v3.12 | OnePlus Nord 2 | Realme x7 Max | Realme GT Neo | UNOFFICIAL | STABLE Updated: 03/08/26 ▪️Download ROM [2.8GB] ▪️Screenshots ▪️Support Group | Discord ➡️ Changelog :- - Initial release ⚠️ Notes: - Gapps | User build - Selinux: enforcing - Signed with release keys - Sony Dolby Atmos (OnePlus UI) Follow @OnePlusNord2Updates | @RealmeX7MaxUpdates | @ar_archive_shan

🔥9

Signed Himanshu R Tyagi

31 Jul 2026, 14:30 UTC298 views9 reactionsread 8 August 2026
Photo

Evolution-X Update (Official) op6893 (denniz/cupida) (31/07/26) By: Liwhy Version: 11.9 (A16 QPR2) [XDA] [Download] SHA256: 50d1918d2229035ffd22ab6b04f792ab9bf6c9692be866f820b5324018ed9615 Changelog: - Initial official build - Synced with latest rom changes - July security patches Note: - Due to the migration to official signing keys, only future builds will be eligible to be automatically installed as system upda

🔥81

Signed Himanshu R Tyagi

10 Jun 2026, 18:06 UTC≈1,030 views3 reactionsread 8 August 2026
Photo

Evolution-X (Unofficial) (10/06/26) op6893 (denniz/cupida) By: Liwhy Version: 11.8 (A16 QPR2) [Download] SHA256: 508b9bcd06d9b1bb2ef6d2adeff4ec98caf695c14d8a59ff71145d1777563e1d Changelog: - Fixed nfc unavailable issue - Synced with latest rom changes - June security patches * userdebug, signed, vanilla kernel

3

Signed Himanshu R Tyagi

9 Jun 2026, 06:56 UTC994 views7 reactionsread 8 August 2026
Photo

#LineageOS #ROM #op6893 #Unofficial LineageOS Unofficial - 23.2 for Realme X7 Max and OnePlus Nord 2 | Android 16 By - @ManshuTyagi ▪️ Download ▪️ Donate Changelog: • June Security Patch • Fixed wpa3 wifi & hotspot issues • Misc Improvements Join for Updates - Join

4🔥3

Signed Himanshu R Tyagi

7 Jun 2026, 12:11 UTC857 views2 reactionsread 8 August 2026
Photo

#AxionAOSP #ROM #op6893 #Unofficial Axion AOSP Unofficial - 2.7 for Realme X7 Max and OnePlus Nord 2 | Android 16.2 By - @zatvio ▪️ Download ROM ▪️ Donate Axion AOSP Features Source Changelogs Device CL: • Updated powerhints • Resolve libperfmgr & sepolicy issues • Disabled 6GHz Wi-Fi support via RRO. • Configured SoftAP SAE support. Features • Oplus Camera by @liwhy1 • Revanced Apps • Non-rooted build Note: Di

2

Signed Himanshu R Tyagi

28 May 2026, 14:30 UTC969 views7 reactionsread 8 August 2026
Photo

Evolution-X Update (Unofficial) op6893 (denniz/cupida) (28/05/26) By: Liwhy Version: 11.7 (A16 QPR2) [Download] SHA256: 04a0fdf8c43922c83e00e6cb9106072509e282e10bda239ce24bd3ffc0bca656 Changelog: - Fixed wpa3 wifi & hotspot issues - Added a more consistent fp brightness patch - Cleaned up overlays - Removed dead powerhint entries - Resolved some sepolicy denials - Minor improvements - Synced with latest rom changes

🔥43

Signed Himanshu R Tyagi

26 May 2026, 14:46 UTC≈1,020 views7 reactionsread 8 August 2026
Photo

#LunarisAOSP #OFFICIAL #ROM #op6893 LunarisAOSP 3.10 | OFFICIAL | OnePlus Nord 2 | Realme X7 Max | Realme GT Neo By Rakhshan Build type: Gapps Release date: 26-05-2026 ▪️Download ▪️Changelogs | Device ▪️Support Join: @lunaris_hub Follow: @lunaris_update

🔥42😁1

Signed Himanshu R Tyagi

11 May 2026, 06:31 UTC≈1,100 views8 reactionsread 8 August 2026
Photo

#PixelOS #ROM #op6893 #Unofficial PixelOS Unofficial - 16.2 for Realme X7 Max and OnePlus Nord 2 | Android 16 By - @liwhy1 & @ManshuTyagi ▪️ Download ▪️ Donate Changelog: • Initial A16 Release Join for Updates - Join

🔥53

Signed Himanshu R Tyagi

7 May 2026, 17:28 UTC≈1,060 views4 reactionsread 8 August 2026
Photo

Evolution-X Update (Unofficial) op6893 (denniz/cupida) (07/05/26) By: Liwhy Version: 11.7 (A16 QPR2) [Download] SHA256: 9bee9bfbf97f9d72efc507744e5c36bf47a1eb875f67a06cdc94e5df3beed3ea Changelog: - Improved udfps behaviour - Migrated bt and thermal service to aidl - Updated blobs to latest stock - Resolved most opluscam crashes - Synced with latest rom changes - May security patches * userdebug, signed, vanilla ke

4

Signed Himanshu R Tyagi

7 May 2026, 04:02 UTC983 views4 reactionsread 8 August 2026
Photo

#LineageOS #ROM #op6893 #Unofficial LineageOS Unofficial - 23.2 for Realme X7 Max and OnePlus Nord 2 | Android 16 By - @ManshuTyagi ▪️ Download ▪️ Donate Changelog: • May Security Patch • Fixed Bottom Speaker for Cupida • Misc Improvements Join for Updates - Join

4

Signed Himanshu R Tyagi

17 Apr 2026, 14:27 UTC≈1,190 views10 reactionsread 8 August 2026
Photo

#AxionAOSP #ROM #op6893 #Unofficial Axion AOSP Unofficial - 2.5 for Realme X7 Max and OnePlus Nord 2 | Android 16.2 By - @zatvio ▪️ Download Stock Boot Image(non-rooted) ▪️ Download ROM ▪️ Donate Axion AOSP Features Source Changelogs Changelogs • Added Oplus Camera by @liwhy1 • Non-rooted build • Shipped with Revanced Apps • Test and tell Clean Flash Mandatory Join @zatviobuilds to see all my builds

🔥62🏆1👌1

Signed Himanshu R Tyagi

Showing the 12 most recent of 20 posts we hold for @OnePlusNord2Updates. 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,062,775 of 1,151,006entries 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.

Mentions

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

“OnePlus Nord 2 | Updates” (@OnePlusNord2Updates), 967 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/OnePlusNord2Updates.

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.