Channel
@jamap2p
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
967subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002260457630 |
|---|---|
| Type | Channel |
| Username | @jamap2p |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 7 August 2026 |
| On Telegram | t.me/jamap2p |
Marketing & affiliate — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 46% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 2 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @jamap2p/822 · this entry23 Jul 2026, 13:19 UTC | @slezi_1win/101625 Jul 2026, 16:14 UTC | 1.00 | 2 days |
| @big_pdf_check/107023 Jul 2026, 13:19 UTC | @jamap2p/822 · this entry23 Jul 2026, 13:19 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @slezi_1win | 5 (5/5 hand-verifiable sample passed) | 1.00 | 34 minutes | @slezi_1win (4–1) |
| @big_pdf_check | 5 (5/5 hand-verifiable sample passed) | 1.00 | under a minute | @big_pdf_check (4–1) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 1 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 16 comparable posts for this entry, running 30 May 2026 to 6 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 3, the earliest publisher we hold is @big_pdf_check. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_mutual, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 12:41 | 967 | no change |
| 7 Aug 2026, 06:17 | 967 | first reading |
16 posts held, back to 30 May 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 1 pageof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 3 of 7 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 16 (30 May 2026 – 6 August 2026) |
| Views total | 1,005 |
| Reactions total | 4 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 06:17 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
33 reactions across 10 posts, in 6 distinct kinds. The most used accounts for 42.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 14 | 42.4% | |
| 👍 | 11 | 33.3% | |
| 🔥 | 3 | 9.09% | |
| custom 5309922661374119573 | 2 | 6.06% | |
| custom 5408945262687185722 | 2 | 6.06% | |
| custom 5361876269413721642 | 1 | 3.03% |
Custom emoji. 3 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.
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 10 of the 16 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 33reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 30 May 2026 to 6 August 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.
Марафон по метчу на SERENA. День 3 Цифры за 5 августа: Обработано: 40.231$ Выручка: 2856$ Фейк чеки: 0$ ЗП операторов: 607$ Чистая прибыль: 1891$ Мне начали писать владельцы других площадок, чтобы забирать объём у них по PDF входу и пытаются схантить, предлагая ставки на 1-2% выше. Отвечу тут публично, ребят, вопрос не в %, а в качестве трафика. Если площадки начинают предлагать ставки выше рынка, то у меня всегда…
1058$ заработано за 4 августа. Марафон по метчингу на SERENA день 2 Цифры за 4 августа: обработано 22.356$ выручка 1058$ зп операторов 344$ фейк чеков 0$ кол-во операторов в работе 4 конверсия 69% чистая прибыль 714$ Чистый спред выходит ~5% из-за того, что ~2.5-3% команда теряет на доливах. Пообщались с командой, чтобы она переливала реквизиты со входа, чтобы выплата была не точь в точь, а чуть больше, чтобы не т…
custom 53618762694137216421
60%+ конверсия на чеки от 10к по входу с PDF на SERENA На SERENA есть невыдача 2-2.5млн р / сутки чеками от 10к. Кому нужны хайчеки по ПДФ, пишите, поставлю: @FumoMentor Готов выдать токены 1к1. Сколько токенов берёте в работу на чеки ДО 10к, столько же токенов выдам на чеки ОТ 10к.
❤1
Набор тимлидов на SERENA по PDF Что SERENA готова предложить вашим командам? • страховой 100$ • конверсия 70-75% • время на исполнение заявки 10-15 минут, в зависимости от мерча • почти все мерчи несут ФО за фейк чеки, но фейков крайне мало, работают только со вторичкой • % для команд и тл обсуждается отдельно Тимлиды, кто будет забирать > 10к$/сутки также SERENA даст выплаты, которые можно дробить на 4 чека с фин…
👍2
10.277$ выручка за 7 дней по метчу на SERENA Цифры за 7 дней марафона: оборот: 150.757$ выручка: 10.277$ зп операторов: 3220$ скам: 163$ (2 фейк чека из 2380 сделок, оба фейка компенсированы мерчами) чистая прибыль: 7525$ конверсия за 7 дней: 71.2% также наконец-то серена вчера внедрила бота, который кидает чеки в боте и их не приходится каждый раз качать с сайта, что облегчает работу) встать на серену @closed_e…
К слову о метчинге. Ребят, бегите с площадок где кидают жалобы со входа с ПДФ, а также если у вас за день проскакивает 2-3 фейк чека, т.к скорее всего такие площадки льют первичный трафик. Легко это можно понять по конверсии, если конверсия 40-60%, то с большой вероятностью это первичка, т.к на вторичке конверсия 70%+ И работа с первичным трафиком черевата как раз тем, что поступают жалобы, недоплаты, фейк чеки, от…
24.084$ обработано по метчингу за 17.07 на площадке SERENA Марафон. День 2 Цифры офиса: • обработано 24.084$ • выручка 1910$ • зп 600$ • скамы 43$ (но косяк сотрудника, т.к подтвердил заявку, где чекер показал не валидный чек, поэтому полностью списали с оператора) чистая прибыль: 1310$ Полдня не было больших выплат, поэтому работали мелочью, но достаточно быстро её закрывали, так лило хорошо на входе) Под вечер …
Есть 8-10кк/сутки свободного объёма по входу с PDF Очень хорошо льёт в диапозонах 1-10к, поэтому кто работает на мелких чеках, мой рекомендасьён) Весь трафик качественный, без жалоб и фейк чеков, что очень хорошо помогает сохранять выплаты, чтобы у вас их никто не отобрал. Видели сейчас ТМ закручивает гайки по выплатам? Или на Кае пропали выплаты в несколько чеков? Или другие платёги вводят санкции за то, что если…
❤1
обратите внимание! все те, кто работают по билайну, аккуратнее, лудики начали с софтом залетать в лк и блокать симку даже если вы нажали «отмена» лудик заходит в лк без подтверждения софтом, блокают симку по глухому, и дальше уже понятно что будет с деньгами на симке
Заработал 230.000р за 21 день Делюсь обещенным постом как сейчас живут ЛК по КА и какая выходит математика. Стоим на площадке SERENA с 3 июня по 24 июня залило на 12 кабинетов: 2.870.329р • ставка 8% • заработано 230.000р • потрачено на лк 360.000р • работа в нал • ещё все кабинеты живые В среднем по нашему опыту сейчас ЛК сбера живут от 2млн р, эта сумма заливается ~2 месяца на ЛК То есть математика сберов выхо…
👍3🔥1
Контрагенты Вижу, что многие каналы хайпят это направление и говорят, что оно лучшее для работы по картам. Так ли это на самом деле? Что лучше откатать сбер в 2млн за 2-3 месяца или какой-нибудь тир2 банк в 1кк за 3-4 дня? Конечно второе) Но второе часто работает не стабильно, поэтому если говорить про стабильность, то КА - это самый стабильный метод, который едет на протяжении всего времени, как площадки внедрили…
👍4❤3custom 53099226613741195732
🕊️ Отдых — это часть работы. Без пауз даже самая сильная мотивация быстро превращается в выгорание. Чтобы добиваться лучших результатов, нужно уметь не только работать, но и вовремя восстанавливать силы.
Showing the 12 most recent of 16 posts we hold for @jamap2p. 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 — 319,557 of 1,151,006entries 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.
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“Jama_P2P” (@jamap2p), 967 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/jamap2p.
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.