Telegram RegisterThe public register of Telegram
Telegram profile photo for Nexo Store

Channel

Nexo Store

@Nexo_Stores

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

2,313subscribers

-36 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003453942774
TypeChannel
Username@Nexo_Stores
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/Nexo_Stores

Topic

Ecommerce storefront — 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 86% 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 (1 of the pairs behind the counts below)
Posted firstThenOverlapGap
@Nexo_Stores/1685 · this entry5 Aug 2026, 11:05 UTC@NoobVellenLikes/33645 Aug 2026, 11:05 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@NoobVellenLikes6 (6/6 hand-verifiable sample passed)1.00under a minutethis 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. None of the 0 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 10 comparable posts for this entry, running 4 August 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).

Across the whole group of 2, the earliest publisher we hold is @Nexo_Stores — 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 7 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

2,3132,3822,347.57 August 2026 — 2,349 subscribers7 August 2026 — 2,350 subscribers11 August 2026 — 2,340 subscribers14 August 2026 — 2,351 subscribers17 August 2026 — 2,363 subscribers20 August 2026 — 2,365 subscribers23 August 2026 — 2,374 subscribers26 August 2026 — 2,369 subscribers30 August 2026 — 2,382 subscribers2 September 2026 — 2,369 subscribers6 September 2026 — 2,353 subscribers11 September 2026 — 2,336 subscribers15 September 2026 — 2,316 subscribers18 September 2026 — 2,313 subscribers7 August 202618 September 2026
14 measurements spanning 42 days, net -36. 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 2,303–2,392 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 23:012,313-3
15 Sept 2026, 01:022,316-20
11 Sept 2026, 08:392,336-17
6 Sept 2026, 15:352,353-16
2 Sept 2026, 12:152,369-13
30 Aug 2026, 06:322,382+13
26 Aug 2026, 22:452,369-5
23 Aug 2026, 13:182,374+9
20 Aug 2026, 08:342,365+2
17 Aug 2026, 16:552,363+12
14 Aug 2026, 19:072,351+11
11 Aug 2026, 03:212,340-10
7 Aug 2026, 22:112,350+1
7 Aug 2026, 17:182,349first reading

Engagement

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

Reaction mix

32 reactions across 10 posts, in 8 distinct kinds. The most used accounts for 31.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 62916685450465821311031.3%
custom 5474542646091355558618.8%
515.6%
👏412.5%
🔥39.38%
💯26.25%
👍13.13%
😍13.13%

Custom emoji. 2 of the rows above are 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 are Telegram’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 10 of the 15 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 32 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 15 most recent posts we hold, published 4 August 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, 05:09 UTC181 views3 reactionsread 7 August 2026

🚀 TELEGRAM STARS FOR SELL 🚀 ⭐ 400 Stars Available 💰 Only 1.3₹ Each Star 💸 Total Amount : 520₹ ✔️Source : Og Fragment Stars 🎁 Buy Telegram Stars For • Gifts & Reactions • Premium Content • Channel Support • Telegram Mini Apps ✅ Instant Transfer 📩 DM: @NEXO_247 ✅

👏1custom 54745426460913555581custom 62916685450465821311

5 Aug 2026, 18:26 UTC52 views3 reactionsread 7 August 2026

🔥 Free Fire 1K+ VIP Likes – Available 🔥 🇮🇳ONLY FOR INDIAN SERVER🇮🇳 😏 1000+ LIKES – ₹200 ❌ 99₹✅ Offer Only For Today ⚡️ Instant Likes • No Ban Risk 💬 DM for Buy : @NEXO_247 ✅ Only

👏1custom 54745426460913555581custom 62916685450465821311

5 Aug 2026, 11:32 UTC100 views3 reactionsread 7 August 2026
Forwarded from @NEXO_FF_PROOFSPhoto

1000+ Craftland Followers Sold ✅ Dm For Buy Likes And Followers @NEXO_247 ✅

🔥1custom 54745426460913555581custom 62916685450465821311

5 Aug 2026, 11:24 UTC80 views3 reactionsread 7 August 2026
Forwarded from @NEXO_FF_PROOFSPhoto

1000+ Craftland Followers Sold ✅ Dm For Buy Likes And Followers @NEXO_247 ✅

1custom 54745426460913555581custom 62916685450465821311

5 Aug 2026, 11:05 UTC93 views2 reactionsread 7 August 2026

🚨Price Update Alert! Craftland Followers ke prices jaldi increase hone wale hain due to limited remain. 📈 Agar buy karna hai, abhi best time hai. Price badhne se pehle apna order confirm kar lo! ⚡ ✉️ DM: @NEXO_247✅

2

5 Aug 2026, 10:52 UTC28 views4 reactionsread 7 August 2026
Photo

🚀 CRAFTLAND 1000+ FOLLOWERS 🚀 🔥 JUST ₹999 ONLY! 🔥 ✅ 1000+ REAL FOLLOWERS ⚡ FAST DELIVERY 💯 SAFE & TRUSTED SERVICE 📩 DM NOW: @NEXO_247✅ ⚠️ LIMITED-TIME OFFER!

custom 547454264609135555821custom 62916685450465821311

5 Aug 2026, 03:27 UTC67 viewsread 7 August 2026
Photo

📣 VIP AutoLikes Available! ⚡ 200 Likes Per Day ✉️ DM @NEXO_247 ✅ 🔗 Group Link: https://t.me/Nexo_Autolikes

5 Aug 2026, 03:27 UTC64 viewsread 7 August 2026

📢FREE FIRE AUTO LIKE SERVICE 📢 💵 PRICE LIST (280+ LIKES DAILY) ₹25 ($0.3) ❤️‍🔥280+ Likes ₹160 ($1.9) • 15 Days ❤️‍🔥 4,200+ Likes ₹300 ($3.5) • 30 Days ❤️‍🔥 8,400+ Likes ₹580 ($6.8) • 60 Days ❤️‍🔥 16,800+ Likes ₹1100 ($12.8) • 120 Days ❤️‍🔥 33,600+ Likes ₹1350 ($15.7) • 150 Days ❤️‍🔥 42,000+ Likes ₹3100 ($36.0) • 365 Days ❤️‍🔥 102,200+ Likes 🇮🇳 Region: India Only ⚡ Daily Automatic 280+ Likes ✉️ DM For Buy: @NEXO_

5 Aug 2026, 03:26 UTC33 viewsread 7 August 2026
Forwarded from @NoobVellenLikesPhoto

🚀 CRAFTLAND 1400+ FOLLOWERS 🚀 🔥 JUST ₹777 ONLY! 🔥 ✅ 1400+ REAL FOLLOWERS ⚡ FAST DELIVERY 💯 SAFE & TRUSTED SERVICE 📩 DM NOW: @NoobVellen ✅ ⚠️ LIMITED-TIME OFFER!

4 Aug 2026, 16:54 UTC79 views3 reactionsread 7 August 2026

🗿 Introducing VIP Likes ! 👍Per Day 500+ Likes ! Supported Server :- RU🇷🇺,CIS🇷🇺 ,ID🇮🇩,VN🇻🇳,EU🇪🇺,SG🇸🇬,TW🇹🇼,ME🇳🇬,PK🇵🇰,BD🇧🇩 ✅VIP Like Group : @Nexo_Autolikes ➡️/like1 region uid ⚡️⚡️⚡️⚡️⚡️⚡️⚡️ ☝️VIP Autolikes ! 🗿Daily Automatic 500 Likes ! 🔻 500 Likes : 0.65$ • 45⭐️ 🔻 5K Likes : 4.2$ • 400⭐️ 🔻 10K Likes : 7.8$ • 750⭐️ 🔻 15K Likes : 11.8$ • 1100⭐️ 🔻 30K Likes : 22.2$ • 2100⭐️ 🔻 50K Likes : 36.5$ • 3400⭐️ 🔻 100K Like

👍1💯1custom 62916685450465821311

4 Aug 2026, 11:13 UTC184 views5 reactionsread 7 August 2026

🚀FF PANEL AVAILABLE 🛒 PC Panel 1. Silent - Exe 2. Silent - Kill 3. Lib Bypass 4. Emulator bypass 5. Uid emulator bypass 6. Basic panel 7. Aimsilent - Exe 8. Aimkill Max 9. Br - Mods - Pc 10. Custom panels 🛒 Phone Panel 1. IOS - Flourite FF 2. Br Mods Phone 3. Dripclient FF 4. Haxx-cker Pro FF 5. Hg Cheafs FF 6. Pato - Team FF 7. Pri

custom 629166854504658213121👏1🔥1

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

Names

Channels on the register whose handles appear in this channel's posts.

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

“Nexo Store” (@Nexo_Stores), 2,313 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/Nexo_Stores.

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.