16 Aug 2025, 13:37 UTC383 viewsread 25 August 2026
Ts + Nestjs portfolio is coming ...
Channel
NodiJa - برنامه نویس
@dev_Nodija
On this record: Growth · Engagement · Posts · Telegram's recommendations · Cite this entry
1,101subscribers
-6 since we began measuring on 25 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001490099087 |
|---|---|
| Type | Channel |
| Username | @dev_Nodija |
| Created | 6 August 2021 — measured — dated from the channel’s first post |
| First recorded | 25 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/dev_Nodija |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 17:58 | 1,101 | -5 |
| 26 Aug 2026, 09:03 | 1,106 | -1 |
| 25 Aug 2026, 10:30 | 1,107 | first reading |
Engagement
5 posts held, back to 6 August 2021 — 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 pageof 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 5 posts for this entry, the most recent from 16 August 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
16 Aug 2025, 13:36 UTC380 viewsread 25 August 2026
Node + express portfolio : https://github.com/GodsSajjad/Book-project-backend
16 Aug 2025, 13:29 UTC382 viewsread 25 August 2026
سلام من سجاد هستم و حدود 2.5 سال هست در حوضه بک اند سایت ، API های تلگرام ، هوش مصنوعی و استفاده از دیتابیس های MySql PostgresSql, Mongodb فعالیت دارم مسلط به git , GitHub برای کارهای گروهی توانایی ها : بک اند سایت با : JS + express Or TS + Nestjs ربات تلگرام با : TS رفع باگ های دیتابیس های رابطه ای (SQL) To contact me : @GodsSajjad
16 Aug 2025, 13:11 UTCviews —
Channel photo removed
6 Aug 2021, 11:09 UTCviews —
Channel created
Showing the 5 most recent of 5 posts we hold for @dev_Nodija. 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.
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.
✨نگين عابدزاده✨
@Negin_abedzade · 63,136
Telegram ranks this channel #52 of 52 here — alongside 51 others — read 25 August 2026
@Negin_abedzade · 63,136
Telegram ranks this channel #52 of 52 here — alongside 51 others — read 25 August 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list 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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“NodiJa - برنامه نویس” (@dev_Nodija), 1,101 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/dev_Nodija.
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.