6 Aug 2026, 18:35 UTC≈1,020 viewsread 13 August 2026
If any real Meta employee or authorized support agent sees this message and can assist, please message me directly Serious and legitimate help only Contact- @TGAshwyn 🧑💻
Channel
@OGUAshwyn
@Metaagentneed
On this record: Topic · Growth · Engagement · Posts · Cite this entry
3subscribers
+1 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 | -1003781082139 |
|---|---|
| Type | Channel |
| Username | @Metaagentneed |
| Created | 17 March 2026 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 3 times, most recently 11 October 2026 |
| On Telegram | t.me/Metaagentneed |
Topic
Other / unclassifiable — 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 3 October 2026 and assigned it the closest of 31 fixed categories, at 99% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 08:37 | 3 | -1 |
| 16 Aug 2026, 15:53 | 4 | +2 |
| 13 Aug 2026, 19:36 | 2 | no change |
| 7 Aug 2026, 18:51 | 2 | first reading |
Engagement
4 posts held, back to 17 March 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 4 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
20 Mar 2026, 21:55 UTC≈2,720 viewsread 13 August 2026
If any real Meta employee or authorized support agent sees this message and can assist, please message me directly Serious and legitimate help only Contact- @TGAshwyn ✅
18 Mar 2026, 15:11 UTC≈1,120 viewsread 13 August 2026
NEED META AGENT 📱 I am looking for a genuine Meta support agent or Meta employee who can help with Facebook and Instagram account unbans. I have over 100 disabled/unbanned accounts that need review. I am willing to pay good $$$ per successful unban. If any real Meta employee or authorized support agent sees this message and can assist, please message me directly Serious and legitimate help only Contact- @TGAshwy…
17 Mar 2026, 13:52 UTCviews —
Channel created
Showing the 4 most recent of 4 posts we hold for @Metaagentneed. 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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“@OGUAshwyn” (@Metaagentneed), 3 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/Metaagentneed.
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.