Channel
@Projectoid
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry
264subscribers
+0 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001965093628 |
|---|---|
| Type | Channel |
| Username | @Projectoid |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 9 August 2026 |
| On Telegram | t.me/Projectoid |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 14:21 | 264 | no change |
| 9 Aug 2026, 07:18 | 264 | first reading |
18 posts held, back to 20 February 2025 — 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 18 posts for this entry, the most recent from 23 February 2026. An engagement rate over an empty window would be a number about nothing.
25 reactions across 9 posts, in 8 distinct kinds. The most used accounts for 52.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 13 | 52.0% | |
| 🏆 | 3 | 12.0% | |
| 👨💻 | 3 | 12.0% | |
| 🫡 | 2 | 8.00% | |
| 🆒 | 1 | 4.00% | |
| 👌 | 1 | 4.00% | |
| 👏 | 1 | 4.00% | |
| 💯 | 1 | 4.00% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 9 of the 18 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 25reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 20 February 2025 to 23 February 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Projectoid. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 18 most recent posts we hold for this entry, published 20 February 2025 to 23 February 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
✉️ Final Update — Projectoid API Services ‼️ Dear Projectoid Community, Building Projectoid and serving developers across the globe has been an incredible journey. 💙 What started as a small, self-funded passion project turned into something far bigger than we ever imagined. Over this time, we learned countless lessons, explored new ideas, and connected with an amazing community. While our latest APIs did not achie…
🆒1
What next? ❓ 💬 Message to Channel Inbox or Chat
🔼 Update: RESOLVED SSL issue of documentation page! Access it now: 🔗 https://docs.projectoid.in
Posted without readable text
🅿️ Important Info Documentation Page issue will be fixed by our team later on, Until then its accessible at: 🔗 https://api.projectoid.in/docs Regards, Projectoid Team
Project Buildgram 🛄 {Powered by Projectoid} is now live! Built for just You! Go check out @Buildgram ☄️
👍2
🅿️ New Update: Broadcast API v2.0.2 📣 We’ve upgraded the Broadcast API from v2.0.1-beta to v2.0.2! What’s New: • Enhanced speed and stability • Fixed addChat list_id passing issue • Resolved broadcast webhook bug • Added Revoke Auth Key button in @Projectoidbot (under Security, visible under specific conditions) • New: Live Broadcast Stats Dashboard now available at projectoid.in/dashboard/api/broad…
👍2
🅿️ The Broadcast API—one of our most anticipated and widely requested APIs—was initially launched in beta but had stability issues. We’ve been working on a stable and upgraded version, which is now almost ready! However, due to unforeseen circumstances, its release has been delayed by a week or two. Rest assured, we’ll be back with an update very soon! In the meantime, explore our other APIs at docs.projectoid.in.…
🅿️ New API Segment Launch 🆕 🚀 Tools API Segment is Live! Retrieve app details & real-time weather data. 🔹 Supports App Store, Play Store & Weather 🔹 Easy & powerful utilities • Explore & use it now: https://docs.projectoid.in/ • Navigate to the Tools API page (via Next buttons or Sidebar) 👍 @Projectoid • @ProjectoidApi #DevelopedForDevelopers. #BuiltForYou.
🔼 Woohoo! We are on Top Results in top Search Engines. 🥇 Thanks for your Support. Will be getting even better very soon to occupy all the search results & remove the suggest spell correction
🏆3
🅿️ New API Segment Launch 🆕 🚀 Ledger API Segment is Live! Fetch transactions & generate UPI QR codes. 🔹 Supports Paytm & BharatPe 🔹 Secure & fast integration • Explore & use it now: https://docs.projectoid.in/ 👍 @Projectoid • @ProjectoidApi #DevelopedForDevelopers. #BuiltForYou.
👍3
📁 Documentation Path Updated: https://docs.projectoid.in/
Showing the 12 most recent of 18 posts we hold for @Projectoid. 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.
Citation-graph rank — 42,240 of 1,345,403entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 3 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“Projectoid - Designed for Developers. Built for You.” (@Projectoid), 264 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/Projectoid.
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.