BIZTRAC BETA
Activities of adventure companies

TRUESTORY AS

Org. no. 917636907 Limited company (AS) Sarpsborg Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 11.0m
Operating profit NOK −2.8m
Equity NOK −10.6m
Incorporated 2016
Share capital NOK 45,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−10,6 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2,8 mill kr).

TRUESTORY AS is registered as a limited company in Sarpsborg, Østfold with organisation number 917636907. The business is classified under activities of adventure companies (NACE 93.291). The company was incorporated in 2016. Registered share capital is NOK 45,000, divided into 30000 shares. The company's stated purpose is: “Salg av opplevelser samt det som etter styrets skjønn står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.0m in revenue and NOK −2.8m in operating profit.

Key figures · 2025

Revenue
NOK 11.0m
Operating profit
NOK −2.8m
Equity
NOK −10.6m

Financial health · 2025

Liquidity
0.17
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-472.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns TRUESTORY AS?

TRUESTORY APS
TRUESTORY AS
NOK 11.0m rev. · NOK −2.8m profit

TRUESTORY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRUESTORY AS

Who owns TRUESTORY AS?

TRUESTORY APS is the largest registered owner, with 100.0%.

What is the revenue of TRUESTORY AS?

TRUESTORY AS had revenue of NOK 11.0m in 2025.

Who is the general manager of TRUESTORY AS?

Fanny Ponce is registered as general manager of TRUESTORY AS.

Where is TRUESTORY AS based?

TRUESTORY AS has its business address in Sarpsborg.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.