Лонх от 61300 дада нетнет

Channel
Nischeta DAO | Hibachi Maxi
@nischetadao
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
19subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002125923884 |
|---|---|
| Type | Channel |
| Username | @nischetadao |
| Description | Щитпост и слив бабок |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 2 |
| On Telegram | t.me/nischetadao |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 17:46 | 19 | no change |
| 8 Aug 2026, 22:46 | 19 | first reading |
Engagement
20 posts held, back to 4 August 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 20 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- ≈1,340
- Videos
- ≈15
- Links
- ≈263
Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Recent posts
С ARX вышел, не нравится график
Video, posted without a caption
Хрп который я забыл зашортить уже был бы тейк
Давай родненьки, иби эти артификал интеледжинс
Video, posted without a caption
Информативно
Я так понял сам Иисус купил HYPE, потому что других объяснений чем держат его прайс
Video, posted without a caption
Ada можно шортануть, таргет 0.17
Ага, а ебучий CRCL дало палку на 12% без снятия ликвы и теперь пошел раг) ебал я эти стокс маркетс
На самом деле ошибка была в момент плохого понимания отчетности По отчетности епс был на 17% выше реальных, а я на это хуй положил и как раз сейчас оно выросло на 17%
Showing the 12 most recent of 20 posts we hold for @nischetadao. 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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“Nischeta DAO | Hibachi Maxi” (@nischetadao), 19 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/nischetadao.
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.