Telegram RegisterThe public register of Telegram
Telegram profile photo for Nexus - MiddleMan

Channel

Nexus - MiddleMan

@nexusmiddleman

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

18subscribers

-1 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1003127541341
TypeChannel
Username@nexusmiddleman
Created16 November 2025measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live2 September 2026
Measurements held3
Confirmed unchanged3 times, most recently 2 September 2026
On Telegramt.me/nexusmiddleman

Growth

181918.511 August 2026 — 19 subscribers11 August 2026 — 19 subscribers18 August 2026 — 18 subscribers11 August 202618 August 2026
3 measurements spanning 7 days, net -1. 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 18–19 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Aug 2026, 14:3518-1
11 Aug 2026, 17:4619no change
11 Aug 2026, 04:1519first reading

Engagement

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

Recent posts

17 Dec 2025, 14:48 UTC921 viewsread 11 August 2026

My other account @frequent501 is Frozen🧊 New account —> @socrate602

9 Dec 2025, 18:31 UTC761 viewsread 11 August 2026

💚 Bot Finally Working Again ! Make Safe Trades Now —> @nexusmmbot 📊ChangeLog : - Fixed All Errors of withdraw - Improved Security of Funds ( Encrypting key hash of wallets ) - Fixed all major bugs and not logic things ( Don't forget its a beta yet the project is new feel free to dm me for suggestions or bug or support ) ! Bug/Support/Suggestion -> @frequent501

23 Nov 2025, 15:07 UTC≈1,190 viewsread 11 August 2026

⚠️For now, only Litecoin (LTC💲) is accepted on the bot. In the future, BTC / ETH / SOL and others will be accepted. Note that the bot is currently in beta, so if you encounter any bug or issue, please contact: Support / Problems → @frequent501 -> CoOwner : @askineiko ( Don't message him for question / problems ) ⚠️DON’T FORGET: FOR THE PROJECT OPENING, FEES ARE AT $0! 🤖Start a trade at @nexusmmbot

20 Nov 2025, 15:16 UTC≈1,180 viewsread 11 August 2026

Any question or error -> Owner / Support : @frequent501 -> CoOwner : @askineiko

19 Nov 2025, 18:16 UTC≈1,260 viewsread 11 August 2026

🤖 Nexus – Fully Automated Middleman (LTC Only) 💲 Your safety — Our priority. 👑 SPECIAL LAUNCH OFFER: 0 FEES 🔥 All transactions processed with 0 fees (limited time) ⚡️ 100% Automated System – 24/7 ✔️ No manual work ✔️ Always online ✔️ Fast, reliable & secure ⚡️ Ultra Fast Processing 🕞 Deals handled in seconds 📊 Zero delays — instant releases 🛡 Maximum Security 🛡 Anti-scam automation 🛡 Smart verification system

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

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 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.

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

“Nexus - MiddleMan” (@nexusmiddleman), 18 subscribers as measured 18 August 2026. Telegram Register, tgregister.com/channel/nexusmiddleman.

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.