Telegram RegisterThe public register of Telegram
Telegram profile photo for چیت اسکین پابجی موبایل

Channel

چیت اسکین پابجی موبایل

@pubg_Ninja_01

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

7,926subscribers

-359 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001568133684
TypeChannel
Username@pubg_Ninja_01
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live16 September 2026
Measurements held13
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/pubg_Ninja_01

Topic

Gaming — 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@pubg_Ninja_01/3743 · this entry3 Aug 2026, 14:52 UTC@PabgCity_IR/54404 Aug 2026, 12:32 UTC1.0022 hours
@pubg_Ninja_01/3750 · this entry4 Aug 2026, 14:20 UTC@PabgCity_IR/54414 Aug 2026, 14:22 UTC1.002 minutes
@pubg_Ninja_01/3752 · this entry4 Aug 2026, 18:36 UTC@PabgCity_IR/54434 Aug 2026, 18:37 UTC1.00under a minute
@PabgCity_IR/54476 Aug 2026, 19:20 UTC@pubg_Ninja_01/3755 · this entry6 Aug 2026, 19:21 UTC1.00under a minute
@pubg_Ninja_01/3745 · this entry3 Aug 2026, 18:14 UTC@PabgCity_IR/54507 Aug 2026, 18:34 UTC1.004 days
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@PabgCity_IR6 (5/6 hand-verifiable sample passed)1.002 minutesthis entry (42)

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. 1 of the 2 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 15 comparable posts for this entry, running 2 August 2026 to 7 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 @pubg_Ninja_01 — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, 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

7,9268,2868,1067 August 2026 — 8,285 subscribers8 August 2026 — 8,286 subscribers11 August 2026 — 8,275 subscribers14 August 2026 — 8,241 subscribers18 August 2026 — 8,225 subscribers21 August 2026 — 8,203 subscribers24 August 2026 — 8,171 subscribers28 August 2026 — 8,145 subscribers30 August 2026 — 8,097 subscribers3 September 2026 — 8,055 subscribers8 September 2026 — 8,003 subscribers12 September 2026 — 7,963 subscribers16 September 2026 — 7,926 subscribers7 August 202616 September 2026
13 measurements spanning 40 days, net -359. 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 7,872–8,340 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 16:567,926-37
12 Sept 2026, 13:597,963-40
8 Sept 2026, 14:228,003-52
3 Sept 2026, 12:598,055-42
30 Aug 2026, 23:298,097-48
28 Aug 2026, 03:558,145-26
24 Aug 2026, 22:338,171-32
21 Aug 2026, 13:038,203-22
18 Aug 2026, 04:038,225-16
14 Aug 2026, 23:278,241-34
11 Aug 2026, 11:428,275-11
8 Aug 2026, 11:418,286+1
7 Aug 2026, 13:168,285first reading

Engagement

77 posts held, back to 2 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 20 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.42%
avg views ÷ 7,926 subscribers
Avg views / post
271
10 posts measured
Reaction rate
0.457%
reactions ÷ views · ER floor
Posts in window
10
of 77 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. It is computed over the 9 of 10 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 27 August 2026
Posts held77 (2 August 202627 August 2026)
Views total2,708
Reactions total12
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 18:35 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.

Reaction mix

62 reactions across 24 posts, in 9 distinct kinds. The most used accounts for 29.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1829.0%
🕊1829.0%
😈1321.0%
👎46.45%
👍34.84%
❤‍🔥23.23%
💯23.23%
11.61%
🏆11.61%

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

Measured over the 77 most recent posts we hold, published 2 August 2026 to 27 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

27 Aug 2026, 20:28 UTC83 viewsread 28 August 2026

😌𝗪𝗶𝗿𝗲𝗚𝘂𝗮𝗿𝗱 𝗣𝗨𝗕𝗚 وایرگارد پابجی موبایل🪙 🏳️𝗙𝗼𝗿 𝗔𝗹𝗹 𝗡𝗲𝘁𝘀 : 𝐢𝐑𝐚𝐍𝐂𝐞𝐋🛜 - 𝐌𝐜𝐢🛜 - 𝐑𝐢𝐓𝐞𝐋🛜 آیپی / سرور : امارات🇦🇪 📥Download WireGuard📤 ✅بهترین وایرگارد - صدر در صد تضمینی با پینگ پایین و ریجستر تیر فوق‌العاده👑 𝗙𝗼𝗿 𝗔𝗹𝗹 𝗗𝗲𝘃𝗶𝗰𝗲 : 𝐀𝐧𝐝𝐫𝐨𝐢𝐝🤖 - 𝐢𝐏𝐡𝐨𝐧𝐞🍏 - 𝐏𝐜💻 جهت حمایت از ما ریکشن مختلف و شیر کردن پست فراموش نشه😎

Signed - R e Z a

25 Aug 2026, 19:49 UTC201 views1 reactionsread 28 August 2026

😌𝗪𝗶𝗿𝗲𝗚𝘂𝗮𝗿𝗱 𝗣𝗨𝗕𝗚 وایرگارد پابجی موبایل🪙 🔴قابلیت های وایرگارد : 📣پینگ پایین و سرعت بالا🛜 📣ریجستر مرگبار داخل گیم🛜 📣بدون دیلی و قطعی🛜 📣حجم 100 گیگ - کاربر نامحدود🛜 🔄Download WideGuard🔄 📝Server : USA🇺🇸 سازگار روی ایرانسل🛜 - همراه اول🛜 - رایتل🛜 برای حمایت از ما ریکشن فراموش نشه❤️

😈1

Signed - R e Z a

24 Aug 2026, 20:01 UTC259 views1 reactionsread 28 August 2026

😌𝗪𝗶𝗿𝗲𝗚𝘂𝗮𝗿𝗱 𝗣𝗨𝗕𝗚 وایرگارد پابجی موبایل🪙 🏳️𝗙𝗼𝗿 𝗔𝗹𝗹 𝗡𝗲𝘁𝘀 : 𝐢𝐑𝐚𝐍𝐂𝐞𝐋🛜 - 𝐌𝐜𝐢🛜 - 𝐑𝐢𝐓𝐞𝐋🛜 آیپی / سرور : امارات🇦🇪 📥Download WireGuard📤 ✅بهترین وایرگارد - صدر در صد تضمینی با پینگ پایین و ریجستر تیر فوق‌العاده👑 𝗙𝗼𝗿 𝗔𝗹𝗹 𝗗𝗲𝘃𝗶𝗰𝗲 : 𝐀𝐧𝐝𝐫𝐨𝐢𝐝🤖 - 𝐢𝐏𝐡𝐨𝐧𝐞🍏 - 𝐏𝐜💻 جهت حمایت از ما ریکشن مختلف و شیر کردن پست فراموش نشه😎

😈1

Signed - R e Z a

24 Aug 2026, 14:16 UTC264 views1 reactionsread 28 August 2026

گرفتی این پنل وایرگارد خفنو رفیق؟🫦☑️

👍1

Signed - R e Z a

23 Aug 2026, 18:42 UTC305 views2 reactionsread 28 August 2026
Photo

بهترین پنل وایرگارد ک میتونی وایرگارد رایگان تولید کنی🔥🎁 و حتی بفروشی و ازش پول در بیاری کاملا به صورت رایگان برات آوردم💞☑️ ❌ Download panel ❌ 🕯 قابلیت پنل وایرگارد : 🔥ساخت وایرگارد به تعداد نامحدود 🔥تعیین حجم و کاربر 🔥تعیین مدت زمان کانفینگ و... ریکشن مختلف یادت نره عشق داداش👩‍❤️‍💋‍👨☑️

🏆1😈1

Signed - R e Z a

23 Aug 2026, 15:15 UTC277 views1 reactionsread 28 August 2026

❤️وایرگارد پابجی موبایل❤️ ▫️ 𝗪𝗜𝗥𝗘𝗚𝗨𝗔𝗥𝗗 𝗣𝗨𝗕𝗚 ▫️ ▫️ سرور :سنگاپور🇸🇬 ▫️ مناسب برای: همراه اول - ایرانسل - رایتل 🌐کانفینگ اختصاصی خود را دریافت کنید🛡 💎𝗥𝗘𝗖𝗘𝗜𝗩𝗘 𝗪𝗜𝗥𝗘𝗚𝗨𝗔𝗥𝗗💎 مخصوص لاگین و پلی دادن❤️ با ری اکشن های زیباتون به ما انرژی زیادی میدید💔❤️

😈1

Signed Parsa

22 Aug 2026, 19:48 UTC304 views1 reactionsread 28 August 2026

😌𝗪𝗶𝗿𝗲𝗚𝘂𝗮𝗿𝗱 𝗣𝗨𝗕𝗚 وایرگارد پابجی موبایل🪙 🏳️𝗙𝗼𝗿 𝗔𝗹𝗹 𝗡𝗲𝘁𝘀 : 𝐢𝐑𝐚𝐍𝐂𝐞𝐋🛜 - 𝐌𝐜𝐢🛜 - 𝐑𝐢𝐓𝐞𝐋🛜 آیپی / سرور : امارات🇦🇪 📥Download WireGuard📤 ✅بهترین وایرگارد - صدر در صد تضمینی با پینگ پایین و ریجستر تیر فوق‌العاده👑 𝗙𝗼𝗿 𝗔𝗹𝗹 𝗗𝗲𝘃𝗶𝗰𝗲 : 𝐀𝐧𝐝𝐫𝐨𝐢𝐝🤖 - 𝐢𝐏𝐡𝐨𝐧𝐞🍏 - 𝐏𝐜💻 جهت حمایت از ما ریکشن مختلف و شیر کردن پست فراموش نشه😎

😈1

Signed - R e Z a

22 Aug 2026, 18:45 UTC306 views1 reactionsread 28 August 2026
Photo

⭕️بهترین کانفینگ وایرگاد📱 و 🔑کاملا رایگان برای شما✅ ✅با بهترین پینگ و ریجستر در این وضعیت بد اینترنت ❤️ کانفیگ وایرگاد ❤️کد دی ان اس ❤️‍🔥فقط با یک کلیک بهترین خودت باش

😈1

Signed ROYAL

21 Aug 2026, 19:34 UTC354 views2 reactionsread 28 August 2026

▫️ چیت پابجی Data موبایل ▫️ ▫️ مخصوص تمامی اندروید ها ▫️ ▫️ ▫️ ▫️ ▫️ ▫️ ▫️ ▫️ ▫️ 📤 برای دریافت فایل 🖇 ▫️ ▫️ ▫️ ▫️ ▫️ ▫️ ▫️ ▫️ 🔮 توضیحات : 🦦⬇️⬇️ 🤩🤩🤩🤩🧥🤩 🤩🤩🤩 🗝 رمز : [ 8080 ❌ ] ▫️ ▫️ ▫️ ▫️ ▫️ ▫️ ▫️ ▫️ ❤️‍🔥‍ GL / KR ❤️‍🔥 ▫️ 32 / 64 ▫️ ▫️ نسخه چیت 4.5▫️ ( #بزن_روی_پیوستن ) ▫️

💯1😈1

Signed - R e Z a

21 Aug 2026, 07:07 UTC355 views2 reactionsread 28 August 2026

😌𝗪𝗶𝗿𝗲𝗚𝘂𝗮𝗿𝗱 𝗣𝗨𝗕𝗚 وایرگارد پابجی موبایل🪙 🔴قابلیت های وایرگارد : 📣پینگ پایین و سرعت بالا🛜 📣ریجستر مرگبار داخل گیم🛜 📣بدون دیلی و قطعی🛜 📣حجم 100 گیگ - کاربر نامحدود🛜 🔄Download WideGuard🔄 📝Server : USA🇺🇸 سازگار روی ایرانسل🛜 - همراه اول🛜 - رایتل🛜 برای حمایت از ما ریکشن فراموش نشه❤️

🔥1😈1

Signed - R e Z a

20 Aug 2026, 21:16 UTC397 views1 reactionsread 28 August 2026

🪙 چیت اسکین دیتا بدون بن🎮 🔘 64/32 🔘 🔘GL/KR 🔘 برای تمامی دیوایس ها📲 🔠🔠🔠🔠🔠🔠🔠🔠🔠🔠 لینک دانلود فایل چیت اسکین🖼 🔠🔠🔠🔠🔠🔠🔠🔠🔠🔠 وسایل پک ▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️ | 🔑 | آموزش زدن چیت اسکین دیتا☝️

😈1

20 Aug 2026, 07:00 UTC424 views1 reactionsread 28 August 2026

مشکل بات درست شد به راحتی چیتو بردارید ✔️

😈1

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

Mentions

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

“چیت اسکین پابجی موبایل” (@pubg_Ninja_01), 7,926 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/pubg_Ninja_01.

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.