Channel
Articles in neonatology
@neonaversity
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,714subscribers
+105 since we began measuring on 26 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001314781997 |
|---|---|
| Type | Channel |
| Username | @neonaversity |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 September 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/neonaversity |
Topic
Health & wellness — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 49% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Nov 2026, 02:01 | 3,714 | +11 |
| 4 Nov 2026, 14:56 | 3,703 | +2 |
| 1 Nov 2026, 14:46 | 3,701 | -1 |
| 29 Oct 2026, 05:48 | 3,702 | +6 |
| 26 Oct 2026, 02:19 | 3,696 | +1 |
| 23 Oct 2026, 09:38 | 3,695 | +5 |
| 20 Oct 2026, 02:10 | 3,690 | +2 |
| 16 Oct 2026, 20:01 | 3,688 | +4 |
| 13 Oct 2026, 13:58 | 3,684 | +12 |
| 7 Oct 2026, 05:42 | 3,672 | +8 |
| 29 Sept 2026, 22:18 | 3,664 | +19 |
| 15 Sept 2026, 17:39 | 3,645 | +3 |
| 11 Sept 2026, 15:36 | 3,642 | +14 |
| 7 Sept 2026, 13:39 | 3,628 | no change |
| 7 Sept 2026, 02:16 | 3,628 | +7 |
| 2 Sept 2026, 11:48 | 3,621 | +6 |
| 30 Aug 2026, 10:07 | 3,615 | +6 |
| 26 Aug 2026, 19:15 | 3,609 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@AhmedManfyJournals · 34,256
Telegram ranks this channel #5 of 73 here — alongside 72 others — read 20 September 2026
@librospediatria · 21,381
Telegram ranks this channel #9 of 79 here — alongside 78 others — read 26 September 2026
@whitearmyofmedicos · 107,633
Telegram ranks this channel #42 of 60 here — alongside 59 others — read 26 August 2026
@intensivistapediatrico · 23,214
Telegram ranks this channel #55 of 73 here — alongside 72 others — read 20 September 2026
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“Articles in neonatology” (@neonaversity), 3,714 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/neonaversity.
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.