Telegram RegisterThe public register of Telegram
Telegram profile photo for PrimeForge

Channel

PrimeForge

@PrimeForgeHQ

On this record: Growth · Engagement · Posts · Citations · Cite this entry

2subscribers

+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-1002653631060
TypeChannel
Username@PrimeForgeHQ
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 August 2026
Last confirmed live17 September 2026
Measurements held3
Confirmed unchanged5 times, most recently 17 September 2026
On Telegramt.me/PrimeForgeHQ

Growth

121.57 August 2026 — 1 subscribers15 August 2026 — 1 subscribers16 August 2026 — 2 subscribers7 August 202616 August 2026
3 measurements spanning 9 days, net +1. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1–2 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 20:382+1
15 Aug 2026, 06:161no change
7 Aug 2026, 17:461first reading

Engagement

19 posts held, back to 7 April 2026the 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 19 posts for this entry, the most recent from 16 April 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

14 Apr 2026, 04:29 UTC23 viewsread 15 August 2026

Any trader or crypto user from India pakistan or Philippines here?

7 Apr 2026, 06:39 UTC8 viewsread 15 August 2026
Forwarded from @cyberghostofficial

🔥 PrimeForge v2.0.30 Pre Released! By: allmightyvortex ⚡ Legendary !bug scare-trap 👁️ Status auto-view + ❌ react 🎵 Stable !yt downloader 👥 Group + private command fixes Repo: https://github.com/allmightyvortex/primeforge-core

7 Apr 2026, 06:39 UTC6 viewsread 15 August 2026
Forwarded from @cyberghostofficialPhoto

PrimeForge Update — Jan 2026 🔧 Fixed: - Crashes caused by outdated store imports — resolved for full compatibility. - “Last seen at” bug after linking — now shows ONLINE as expected. - Status autopilot now works silently: views and reacts only to real statuses, no spam logs. - Removed unnecessary logging to reduce heat and keep execution lean. ⚙️ Added Still Under Development: - QR Code Show In Termux - Cloak mode

7 Apr 2026, 06:39 UTC8 viewsread 15 August 2026
Forwarded from @cyberghostofficial

📜 PrimeForge‑Core WhatsApp Bot Guide 🔌 Connecting to WhatsApp 1. Clone or download PrimeForge‑Core. 2. Install dependencies: bash npm install 3. Start the bot: bash node protocol-core.js 4. A QR code will appear in the terminal. - Open WhatsApp on your phone. - Go to Linked Devices → Link a Device. - Scan the QR code directly. 🌐 Alternative QR Method If you prefer to open the QR in a browser:

7 Apr 2026, 06:39 UTC8 viewsread 15 August 2026
Forwarded from @cyberghostofficial

📢 PrimeForge Bot Tutorial (Early Access) Here’s how to use the bot right now: 1. Clone the repo bash git clone [email protected]:AllMightyVortex/PrimeForge-Core.git cd PrimeForge-Core 2. Install requirements Make sure Node.js is installed, then run: bash npm install 3. Start the bot bash node megatron-locked.js 4. Test and explore - Try basic commands. - Some features may still be

7 Apr 2026, 06:39 UTC8 viewsread 15 August 2026
Forwarded from @cyberghostofficial

📢 Bot Tutorial Reminder Here’s how you can use the bot right now: 1. Get the repo link - PrimeForge-Core (github.com in Bing) 2. Clone the repo In Termux or your PC, run: bash git clone <repo-link> cd <repo-folder> 3. Install requirements - Make sure you have Node.js installed. - Run npm install inside the folder. 4. Start the bot bash node protocol-core.js 👉 This will start the

7 Apr 2026, 06:39 UTC8 viewsread 15 August 2026
Forwarded from @cyberghostofficial

📢 Bot Update Info Here are the current bot links: - 🔗 PrimeForge-Core (github.com in Bing) About the bot: - This project is still in development. - Current repos are for testing and early access. - The official release has not been done yet. How to use: - You can explore the repos, test features, and share feedback. - Updates will keep coming, so stay tuned.

7 Apr 2026, 06:39 UTC4 viewsread 15 August 2026
Forwarded from @cyberghostofficial

https://safibets.com?ref=940568

7 Apr 2026, 06:39 UTC3 viewsread 15 August 2026
Forwarded from @cyberghostofficialPhoto

PHIR SE CHXD GAYE GURU 😭

7 Apr 2026, 06:39 UTC6 viewsread 15 August 2026
Forwarded from @cyberghostofficial

anyone have b3 (braintree) auth site (clean af) take cc chkr access in exchange @DMxABHI_BOT 💎

Showing the 12 most recent of 19 posts we hold for @PrimeForgeHQ. 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

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.

Mentions

Named by 2 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.

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 August 2026 — this entry's latest reading, not the date you are reading this.

“PrimeForge” (@PrimeForgeHQ), 2 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/PrimeForgeHQ.

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.