Ad system
solution.no
33 apps across 14 app-ads.txt files declare solution.no; 97% hold a DIRECT account and 3% list it as a RESELLER. Its sellers.json lists 79 sellers, and 93% of the 14 lines we checked against it match.
- Apps declaring it
- 33
- Sellers in sellers.json
- 79
- Lines verified
- 93%
- Lines with errors
- 1
- Avg. supply path score
- 67.0 / 100
32 DIRECT · 1 RESELLER
0% confidential
13 of 14 checked lines
14 lines in total
33 apps scored
App counts, the sellers.json breakdown and the directory ranking are as of , recomputed daily (the same numbers as the directory). Line counts are recounted every 10 minutes. sellers.json last read 13 October 2026. The supply path score sums up how short and clean the declared paths are, 0 to 100 (how it is computed).
How to add solution.no to app-ads.txt
One line per account, in the app-ads.txt at the root of the domain your App Store and Google Play listings name as the developer website.
solution.no, YOUR_ACCOUNT_ID, DIRECT
solution.no, YOUR_ACCOUNT_ID, RESELLER- Field 1:
solution.no, the domain solution.no uses in app-ads.txt. - Field 2: your account ID with solution.no. It must equal the
seller_idin solution.no's sellers.json. - Field 3: DIRECT if you hold the account, RESELLER if a partner holds it and sells your inventory. DIRECT vs RESELLER
- Field 4 (optional): a certification authority ID. Most lines naming solution.no carry none, or different ones, so we do not suggest one.
sellers.json at a glance
- Status
- Published
- Sellers listed
- 79
- Confidential
- 0 (0%)
- Passthrough
- 0
- Removed, last 30 days
- 0
- Last read
- Oct 13, 2026
- PUBLISHER79
- INTERMEDIARY0
- BOTH0
Cross-check of lines naming solution.no
- Verified 13
- Seller ID not found 0
- DIRECT but intermediary 0
- RESELLER but publisher 1
- Seller type BOTH 0
- Confidential seller 0
- No sellers.json 0
- Unchecked 0
Every line naming solution.no is looked up in its sellers.json. What each status means
Common errors with solution.no lines
-
RESELLER but publisher
1 line
If the account is yours, declare it DIRECT. If a partner holds it, ask solution.no why the account is listed as PUBLISHER.
Apps that declare solution.no
| App | Store | Relationship | Status |
|---|---|---|---|
| Android | DIRECT | Live | |
| Android | DIRECT | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live | |
| iOS | RESELLER | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live |
Questions about solution.no
Does solution.no publish a sellers.json?
Yes. Its file at https://solution.no/sellers.json listed 79 sellers when we last read it on 13 October 2026: 79 publishers, 0 intermediaries and 0 listed as both; 0% are confidential.
How many apps declare solution.no in app-ads.txt?
33 apps in Stoqlab's data (delisted apps included) declare solution.no: 32 with at least one DIRECT line and 1 with at least one RESELLER line, across 14 app-ads.txt files, as of 13 October 2026 (recounted daily).
Why do solution.no lines fail verification?
Of 14 lines naming solution.no, 1 contradict its sellers.json. The most common case is "RESELLER but publisher", on 1 line. If the account is yours, declare it DIRECT. If a partner holds it, ask solution.no why the account is listed as PUBLISHER.
Not sure whether your line should say DIRECT or RESELLER? DIRECT vs RESELLER in app-ads.txt
Sources: the public app-ads.txt files of tracked apps and the sellers.json of solution.no. Something wrong? Tell us.