Telegram RegisterThe public register of Telegram
Telegram profile photo for NotDheeraj06 Updates

Channel

NotDheeraj06 Updates

@NotDheeraj06_Updates

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

389subscribers

+140 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002486697418
TypeChannel
Username@NotDheeraj06_Updates
CreatedBetween 1 October 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live14 November 2026
Measurements held14
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/NotDheeraj06_Updates

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 22 September 2026 and assigned it the closest of 31 fixed categories, at 87% 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 the other topics.

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 in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@NotDheeraj06_Updates/206 · this entry15 Jun 2026, 13:14 UTC@MotoEdge30Updates/45215 Jun 2026, 13:14 UTC1.00under a minute
@MotoEdge30Updates/45327 Jun 2026, 04:15 UTC@NotDheeraj06_Updates/212 · this entry27 Jun 2026, 04:15 UTC1.00under a minute
@MotoEdge30Updates/4559 Jul 2026, 04:48 UTC@NotDheeraj06_Updates/214 · this entry9 Jul 2026, 04:48 UTC1.00under a minute
@NotDheeraj06_Updates/216 · this entry11 Jul 2026, 16:07 UTC@MotoEdge30Updates/45711 Jul 2026, 16:07 UTC1.00under a minute
@MotoEdge30Updates/4592 Aug 2026, 17:56 UTC@NotDheeraj06_Updates/221 · this entry2 Aug 2026, 17:58 UTC1.002 minutes
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@MotoEdge30Updates6 (6/6 hand-verifiable sample passed)1.00under a minute@MotoEdge30Updates (4–2)

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 3 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 15 comparable posts for this entry, running 15 June 2026 to 6 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).

Of the group of 2 channels, the one whose matching posts we hold earliest is @NotDheeraj06_Updates — 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 11 November 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.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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

2493893198 August 2026 — 249 subscribers8 August 2026 — 249 subscribers16 August 2026 — 254 subscribers25 August 2026 — 284 subscribers31 August 2026 — 293 subscribers8 September 2026 — 307 subscribers15 September 2026 — 308 subscribers28 September 2026 — 322 subscribers9 October 2026 — 350 subscribers15 October 2026 — 354 subscribers22 October 2026 — 364 subscribers29 October 2026 — 375 subscribers5 November 2026 — 382 subscribers14 November 2026 — 389 subscribers8 August 202614 November 2026
14 measurements spanning 97 days, net +140. 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 228–410 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Nov 2026, 08:08389+7
5 Nov 2026, 04:37382+7
29 Oct 2026, 12:36375+11
22 Oct 2026, 22:49364+10
15 Oct 2026, 12:44354+4
9 Oct 2026, 05:42350+28
28 Sept 2026, 02:37322+14
15 Sept 2026, 09:18308+1
8 Sept 2026, 12:59307+14
31 Aug 2026, 04:35293+9
25 Aug 2026, 02:46284+30
16 Aug 2026, 17:05254+5
8 Aug 2026, 21:15249no change
8 Aug 2026, 21:02249first reading

Engagement

20 posts held, back to 15 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 page of 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 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
19s
Average length
19s

Measured directly from 1 video 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

218 reactions across 15 posts, in 14 distinct kinds. The most used accounts for 52.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤11552.8%
🔥5324.3%
👏125.50%
💔94.13%
👍73.21%
😨73.21%
🤯52.29%
🍌20.917%
😭20.917%
🥰20.917%
❤‍🔥10.459%
😁10.459%
😢10.459%
🤣10.459%

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 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 218 reactions 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 15 June 2026 to 6 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

6 Aug 2026, 04:39 UTC197 views1 reactionsread 8 August 2026

Sorry for my mistake, Files have been re-uploaded, also updated the link in the previous post Also for KSUN kernel please use 3.3 KSUN apk Thanks for understanding 🙏

❤1

5 Aug 2026, 19:39 UTC199 views4 reactionsread 8 August 2026

If you are facing slow charging in InfinityX beryllium, please flash this kernel https://t.me/NotDheeraj06_Builds/88972?single Please let me know if you are facing any issues. Thanks for understanding 🙏

❤4

4 Aug 2026, 18:39 UTC347 views11 reactionsread 8 August 2026
Photo

#ROM #Beryllium #InfinityX #BKA #OFFICIAL #QPR2 #k4.19 #EOL Project Infinity X | v3.12 | OFFICIAL | Android 16 | EOL Device: POCO F1 - Beryllium Updated: 04/08/'26 ▪️Download ▪️Recovery ▪️Screenshots ▪️Flash Guide ▪️Support Notes: • This will be the Final Android 16 Build, Next InfinityX Update will be Android 17 • Changelogs: Device | Source • Android 16 QPR2 Build • Vanilla Users Please Read this: Here • Kernel 4…

❤8🔥3

2 Aug 2026, 17:58 UTC341 views4 reactionsread 8 August 2026
Photo

#ROM #InfinityX #BKA #OFFICIAL #QPR2 #EOL Project Infinity X | v3.12 | OFFICIAL | Android 16 | EOL Device: Motorola Edge 30 - Dubai Released: 02/08/2026 ▪️Downloads: ROM | Recovery ▪️Screenshots ▪️Support group This will be the Final Android 16 Build, Next InfinityX Update will be Android 17 Notes: • Changelogs: Device | Source • For play integrity, read this: Click here • Gapps and Vanilla Builds Included • For K…

🔥2❤‍🔥1🤯1

15 Jul 2026, 03:12 UTC813 views38 reactionsread 8 August 2026

There is something important that I need to share, from now on My Poco F1 Trees (4.19 based) are private, as much as I like Open Source Trees, it's really hard for me to make my trees private just to be safe from kangers 💔, I will try to forget what happened yesterday and move on. If new builders need to use my trees they can contact me directly I will provide them with the trees. Thanks for Understanding 🙏

❤27👍7🥰2🍌1😢1

14 Jul 2026, 17:01 UTC692 viewsread 8 August 2026

https://t.me/jiro007/97 Bro don't even know what a kanged commit is, and sends this as a proof that I kang commits lol, learn what a kanged commit is and then talk

14 Jul 2026, 16:08 UTC≈1,020 views11 reactionsread 8 August 2026

https://github.com/LineageOS/android_device_motorola_rtwo/commit/a4818c8d23bb58ccfffbb3becce9aa364725a231 https://github.com/KT-beryllium/android_device_xiaomi_beryllium-419/commit/3fd9b6467b52e8fdf29ff4e25bd9edbea6089fee He (Bugjiro688) is back at it again kanging commits and he thinks i don't notice what he is doing, This is not the first time he has done this, not only that, he picked all my common tree commits …

💔9🍌1🔥1

12 Jul 2026, 16:39 UTC907 views22 reactionsread 8 August 2026
Photo

#ROM #InfinityX #BKA #OFFICIAL #QPR2 #k4.19 #EOL Project Infinity X | v3.12 | OFFICIAL | Android 16 | EOL Device: POCO F1 - Beryllium Released: 12/07/2026 ▪️Download: ROM | Recovery ▪️Screenshots ▪️Flash Guide ▪️Support Group This will be the Final Android 16 Build, Next InfinityX Update will be Android 17 Notes: • Changelogs: Device | Source • Android 16 QPR2 Build • Kernel 4.19 Based • Dynamic Partitions • You c…

🔥14❤4👏4

11 Jul 2026, 16:07 UTC544 views3 reactionsread 8 August 2026
Photo

#ROM #InfinityX #BKA #OFFICIAL #QPR2 #EOL Project Infinity X | v3.12 | OFFICIAL | Android 16 | EOL Device: Motorola Edge 30 - Dubai Released: 11/07/2026 ▪️Downloads: ROM | Recovery ▪️Screenshots ▪️Support group This will be the Final Android 16 Build, Next InfinityX Update will be Android 17 Notes: • Changelogs: Device | Source • For play integrity, read this: Click here • Gapps and Vanilla Builds Included • For K…

❤1😁1😭1

10 Jul 2026, 11:07 UTC295 views8 reactionsread 8 August 2026
Forwarded from @MotoEdge30Updates

LineageOS website now has flash tools for fastboot and adb! One improvement it has over Google Platform Tools is sideloading percentage actually goes up to 100% instead of that weird 47% we are used to seeing heh 👍 https://download.lineageos.org/flash/adb

❤7🔥1

9 Jul 2026, 04:48 UTC532 viewsread 8 August 2026
Photo

#Motorola #Dubai #Test Exciting new test build for Motorola Edge 30 - Dubai is up! This Contains fix for Audio distortion at above 75% volume, Dolby Changes, removed FP Changes from previous test build. report the bugs, if any Note: You Can dirty flash over latest official release Downloads: ROM: Here ROM Recovery: Can use official recovery

Showing the 12 most recent of 20 posts we hold for @NotDheeraj06_Updates. 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.

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.

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

“NotDheeraj06 Updates” (@NotDheeraj06_Updates), 389 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/NotDheeraj06_Updates.

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.