Telegram RegisterThe public register of Telegram
Telegram profile photo for تیگنال / @TRADER_QUANTUM / @cryptosniper_signals / neda crypto / مهیار ترید / میم کوین

Channel

تیگنال / @TRADER_QUANTUM / @cryptosniper_signals / neda crypto / مهیار ترید / میم کوین

@NekorayConfig

On this record: Topic · Growth · Engagement · Posts · Cite this entry

160subscribers

-8 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-1002034706945
TypeChannel
Username@NekorayConfig
Created7 December 2023 — measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live7 October 2026
Measurements held7
Confirmed unchanged1 time, most recently 7 October 2026
On Telegramt.me/NekorayConfig

Topic

Crypto & trading — 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 25 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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.

Growth

1601681647 August 2026 — 168 subscribers8 August 2026 — 168 subscribers15 August 2026 — 167 subscribers21 August 2026 — 166 subscribers4 September 2026 — 163 subscribers26 September 2026 — 162 subscribers7 October 2026 — 160 subscribers7 August 20267 October 2026
7 measurements spanning 61 days, net -8. 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 159–169 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Oct 2026, 03:40160-2
26 Sept 2026, 13:16162-1
4 Sept 2026, 05:36163-3
21 Aug 2026, 22:37166-1
15 Aug 2026, 10:36167-1
8 Aug 2026, 15:31168no change
7 Aug 2026, 09:50168first reading

Engagement

2 posts held, back to 7 December 2023 — 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 2 posts for this entry, the most recent from 5 July 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

5 Jul 2025, 23:46 UTC177 viewsread 8 August 2026

عضو بشید داخل میز ترید 👇 https://t.me/+Ua8lT21ZCTIyOWJk

Showing the 2 most recent of 2 posts we hold for @NekorayConfig. 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.

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

“تیگنال / @TRADER_QUANTUM / @cryptosniper_signals / neda crypto / مهیار ترید / میم کوین” (@NekorayConfig), 160 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/NekorayConfig.

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.