Airdrop Finder
/web3 campaign distribution
We publish campaigns, quests and testnets for web3 projects to the Airdrop Finder Telegram channel and its community group network. Every number on this page comes from our own public channel, so you can open the posts and check them yourself.
We have been publishing web3 campaigns in Indonesia since two thousand and eighteen. The first post is still at the bottom of our channel, and the two thousand four hundred and twenty three campaigns we have published since then are still there as well. The channel is the product.
We are not a media outlet and we are not a listing site. Open our channel and you will find no news posts and no token lists, only campaign announcements for the projects we agreed to take on. That is the whole feed.
Projects come to us when they want readers who sign up rather than readers who scroll past. We take a limited number of projects at a time, we screen each one before it goes out, and we publish what happened after it ran. Our results section below shows one campaign that reached ninety seven percent of its target and another that reached seventy six percent, because both numbers are true and both were sent to us.
Every figure on this page comes from our public channel. Open any post and the views, shares and comments are there to count. If a figure does not match what you find, tell us. We correct it.
The two green cards were sent to us by the projects. The grey cards are our own projection, calculated from views and from how often each post was shared, and labelled as a projection on every card. We only publish a project's numbers with their permission, and we never round a figure up.






















Logos are the property of their respective projects and are shown here because we published their campaigns. We add a logo only with the project's permission . if a project asks us to remove one, we remove it the same day.
Indonesian users actively look for testnets, waitlists and points programs. They join in and they come back for the next one, which is why a campaign here behaves differently from a campaign aimed at a passive audience.
Grass, Bybit, OpenSea, Binance, WalletConnect and Jupiter have all run campaigns through this channel. You can find the posts on our public feed.
Reaching Indonesian users costs a fraction of what the same reach costs in Western markets. That gap has been closing for years, which is the honest reason it is worth moving now rather than later.
Market figures come from publicly available industry reports, named above. They are estimates rather than guarantees.
Our channel average is 23,821 views per post, measured across 7,259 posts published between January and August 2026, all of them still visible on our public channel.
If a scheduled post lands below 50% of that average, you get one free repost. It is measured by the public view counter on Telegram, so it needs no private data from either side.
These guarantees cover posts confirmed at least 72 hours in advance. Platform outages and regulatory changes sit outside them, as they sit outside anyone's control.
| What matters | KOL | Local agency | Global media | Twitter ads | Airdrop Finder |
|---|---|---|---|---|---|
| Cost per registration | $5 to $15 | $3 to $10 | $20 to $40 | $8 to $15 CPM, not CPA | $0.25 to $0.55 |
| Indonesian audience | Partly | Yes | No | Partly | Yes |
| Crypto native readers | Yes | Partly | Yes | No | Yes |
| Airdrop and testnet experience | No | No | Partly | No | Yes |
| Verified public track record | Partly | Partly | Yes | Yes | Yes |
| Post campaign report | No | Partly | Yes | Yes | Yes |
| Screening before publishing | No | No | Partly | No | Yes |
| No call needed | Yes | No | No | Yes | Yes |
Swipe the table sideways to see all four alternatives.
Comparison compiled from publicly available industry benchmarks and our own records for January to August 2026. Cost per registration varies by campaign type and is shown as a range rather than a fixed number.
| Campaign | Date | Views | Shares · rate |
|---|---|---|---|
9Chainbest performer Testnet | 31 Aug 2026 | 94,231 | 709 |
QuantumGrid Waitlist | 31 Aug 2026 | 25,882 | 103 |
Canopy Claim portal | 6 Sep 2026 | 25,615 | 90 |
Ammora Beta waitlist | 6 Sep 2026 | 25,442 | 267 |
The Office Waitlist | 6 Sep 2026 | 24,883 | 90 |
JaconLabs Eligibility check | 31 Aug 2026 | 24,824 | 12 |
Axis Task | 6 Sep 2026 | 23,568 | 7 |
Voice Vote | 6 Sep 2026 | 23,526 | 31 |
Hoodnodez Waitlist | 6 Sep 2026 | 22,796 | 56 |
Asentum Incentivized testnet | 6 Sep 2026 | 18,673 | 673 |
Parcel RWA Testnet | 2 Sep 2026 | 16,225 | 128 |
Value X Chain Quest | 1 Sep 2026 | 15,412 | 74 |
You tell us about the project and the goal of the campaign. We check the fit with our audience. One message is enough, and we usually reply the same working day.
Usually: day 1We write the copy per project, no one-size-fits-all template, and set the publishing schedule. You see the copy before it goes out, and we change what you ask us to change.
Usually: day 1 to 2The campaign goes live on the Telegram channel and the community group network as agreed. Most campaigns run for three to seven days.
Usually: from day 3You receive views, engagement and the results you report back, written exactly as they are. If a campaign comes in under target, we tell you first and we decide together what to do next.
Usually: from day 7Timelines depend on how quickly the copy is approved and on the publishing queue, so treat the days above as the usual case rather than a fixed schedule.
We research the team through LinkedIn, X history, past projects and funding databases. Anonymous teams are rejected unless they have strong public evidence behind them.
A funded round is good evidence, and so is a working product, a published plan, or a team that has shipped before. We look at funding rounds through public announcements and funding databases, and where there is no round we look at what the project has built and who is behind it. Most campaigns on this channel came from projects that raised nothing at all, and we posted them because the work in front of us was real. We only turn a project down when there is nothing to look at.
We screen the contract for honeypot patterns, rug-pull signals and unlocked liquidity. If it fails the screen, we do not post it.
We review X mentions, Discord activity and community feedback. Projects flagged by trusted sources are rejected.
We check the campaign promise, airdrop size, TGE date and reward structure, for plausibility. Unrealistic promises are rejected or flagged.
Our promise: if a project we posted is later confirmed fraudulent, we take the post down within 24 hours, we say so in the same channel, and we tell any project that asks us about it. Screening is prevention, not a guarantee. We act the moment we learn something, and we do not wait to be asked.
Posts on our Telegram channel, with copy written per project. Most campaigns run three to seven days and carry three to six posts, and the exact number is agreed with you.
Reward quests, testnets and whitelist sign-ups driven through the community group network.
Group placements we manage, agreed per project. The channel is the part anyone can check publicly, and that is the part we are judged on.
You get a private report page with the link, the views, the shares and any numbers your team sends us after the campaign. It stays private to you, and you can forward it to your own team.
We shape the campaign around your goal, not around a fixed package. That is why the number of posts and the length are set per project.
We do not sell a guaranteed number of sign ups. No channel can honestly sell that. What we do is plan the campaign around the goal, then report what actually happened, including when the result is weaker than we both wanted.
Tell us the goal and the budget range you are working with, and we will come back with what we would run and what it would cost.
Share the project and what the campaign needs to achieve. We will come back with an expected reach and how we would work together. Three lines is enough. You can also check our official site at airdropfinder.com and the verification page.