Channel
@presearchnews
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
5,161subscribers
-129 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001258168906 |
|---|---|
| Type | Channel |
| Username | @presearchnews |
| Created | 1 December 2017 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/presearchnews |
Other / unclassifiable — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 57% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 00:01 | 5,161 | -12 |
| 14 Sept 2026, 23:00 | 5,173 | -20 |
| 10 Sept 2026, 22:20 | 5,193 | -16 |
| 5 Sept 2026, 14:18 | 5,209 | -10 |
| 1 Sept 2026, 12:56 | 5,219 | -6 |
| 29 Aug 2026, 17:56 | 5,225 | -8 |
| 26 Aug 2026, 14:57 | 5,233 | -9 |
| 23 Aug 2026, 11:13 | 5,242 | -8 |
| 19 Aug 2026, 16:17 | 5,250 | -13 |
| 16 Aug 2026, 21:42 | 5,263 | -9 |
| 13 Aug 2026, 03:34 | 5,272 | -10 |
| 10 Aug 2026, 04:57 | 5,282 | -5 |
| 6 Aug 2026, 22:21 | 5,287 | -3 |
| 6 Aug 2026, 13:19 | 5,290 | first reading |
20 posts held, back to 10 July 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 8 pages 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 29 July 2026. An engagement rate over an empty window would be a number about nothing.
110 reactions across 17 posts, in 13 distinct kinds. The most used accounts for 28.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 31 | 28.2% | |
| 😢 | 21 | 19.1% | |
| 💩 | 17 | 15.5% | |
| 🔥 | 12 | 10.9% | |
| ❤ | 10 | 9.09% | |
| 👏 | 5 | 4.55% | |
| 🤣 | 5 | 4.55% | |
| 💯 | 3 | 2.73% | |
| 👎 | 2 | 1.82% | |
| 👌 | 1 | 0.909% | |
| 🕊 | 1 | 0.909% | |
| 🙏 | 1 | 0.909% | |
| 🤯 | 1 | 0.909% |
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 17 of the 20 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 110 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 10 July 2026 to 29 July 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.
PRE Platform Update We have done and are doing everything within our power to keep the platform accessible for as long as possible, and several team members are continuing to help users despite no longer being paid. No one is more saddened by this shutdown than we are. Due to third-party vendors shutting down portions of the backend sooner than anticipated, some users may no longer be able to complete withdrawals th…
😢5❤1
Dear Presearch Community, We're keeping the Presearch platform open for an additional 24 hours, until Tuesday, July 28 at 5:00 p.m. PT, to give everyone more time to access their accounts following the recent redirect issues. Please note that while we will do everything possible to keep the platform accessible through this extended window, we cannot guarantee uninterrupted availability because some third-party vend…
💩15❤4🙏1
Hey everyone! We apologize for the technical issues some of you have experienced with our redirects. As we prepare for the platform’s closure, a few of the redirects we put in place haven’t been working as intended. We’re actively working on fixing the issue and appreciate your patience while we get everything back on track. Thank you for bearing with us!
❤4💩1🤯1
Today, we share the difficult news that Presearch is shutting down, effective immediately. To everyone who searched with us, operated a node, advertised, partnered with us, or supported our mission along the way, thank you. Your belief in independent, privacy-first search has meant more than words can express. For more on why we made this incredibly difficult decision and what it means moving forward, please read o…
😢16🤣5💩1🕊1
Big Tech knows what you searched at 2am, what you almost bought, where you were standing when you typed it. Location. Device fingerprint. Click history. Big Tech cross-references it, packages it, sells it, then targets it back at you. That's the business model behind "free" search. We skip all of it. No accounts. No profiles. No warehouse of your searches sitting on a Big Tech server somewhere. Nothing to collect …
👍8
POV: you wanted a 2-minute YouTube video You got a 45-second ad break instead Don't pay for Premium. Presearch on mobile = YouTube, ad-free, 100% free. https://youtu.be/hZY7EixZmcA?si=6eT3EgC9kaWMWuU_
👍3❤1
We decided to make the hard decision to postpone the Series IV Node License Auction. We don't launch node expansion on hype. We launch it on 1 million searches a day. Let's get there. 💪🏻 Stay Anonymous.
Presearch has a secret feature we don't talk about during business hours. 👀 Open the hamburger. Find the 🌶️. Flip the switch. What happens next is between you and your search bar. 🔥 https://presearch.com/nsfw-mode
👍3👎1
Tired of YouTube ads interrupting everything? We found a little loophole. 👀 Open YouTube in the Presearch mobile browser, press play, and watch uninterrupted… while searching privately when you're done. Ad-free YouTube. Private search. One browser. Try it before someone closes the loophole. 🔓🐼 https://account.presearch.com/apps
🔥2👌1👍1
The little things add up. Presearch keeps getting cleaner, sharper, and easier to use. 🔧🚀 We shipped 9 more UI/UX improvements this weekend—tightening spacing, aligning layouts, standardizing fonts, fixing hover states, and smoothing out the takeover ad experience across desktop and mobile.
👍4🔥3👏1
Your new favorite creator might be one search away. 🔥 The Creator tab in Presearch Spicy Mode makes it easy to discover OnlyFans, Fansly, and other independent creators—without digging through mainstream search results that bury or block adult content. Private search. Direct discovery. No judgment. Search after dark with Presearch Spicy Mode. 🌶️ https://presearch.com/nsfw-mode #SpicyMode #Presearch #OnlyFansCre…
👍2👎1🔥1
Presearch's streak so far: 3 auctions. 3 SELLOUTS. 30M+ PRE gone from circulation. Genesis sold out in under 24 hours. Series III alone pulled 15.7M+ PRE. Series IV drops July 22 at 9 AM PST. Only 75 licenses. Don't sleep on this one. 🫡
Showing the 12 most recent of 20 posts we hold for @presearchnews. 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.
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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Presearch News” (@presearchnews), 5,161 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/presearchnews.
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.