biztrac. BETA
COMPANY REGISTER PROFILE
822196292 ORG. NO. 2025 ACCOUNTS 11 SECTIONS
Active UPDATED 03.10.2026
Computing infrastructure, data processing, hosting and related activities

RUNAGAIN AS

Org. no. 822196292 Limited company (AS) Drammen Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 218,000
Operating profit NOK −4.8m
Equity NOK 4.1m
Incorporated 2019
Share capital NOK 66,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4,8 mill kr).

RUNAGAIN AS is registered as a limited company in Drammen, Buskerud with organisation number 822196292. The business is classified under computing infrastructure, data processing, hosting and related activities (NACE 63.100). The company was incorporated in 2019. Registered share capital is NOK 66,000, divided into 1828956 shares. The company's stated purpose is: “Selskapets virksomhet er utvikling av teknologiplattform for løpere og arrangører og salg av tjenester knyttet til denne plattformen.”. The most recent filed accounts, for the 2025 financial year, show NOK 218,000 in revenue and NOK −4.8m in operating profit.

Former names: NESTE LØP AS

Key figures · 2025

Revenue
NOK 218,000
▼ −74 %
Operating profit
NOK −4.8m
▼ −738 %
Equity
NOK 4.1m
▼ −60 %
Est. value
NOK 7.4m

Financial health · 2025

Liquidity
3.74
Very good
Current assets ÷ current liabilities
Profitability
-42.3%
Not satisfactory
Return on total assets
Solidity
48.0%
Very good
Equity as a share of total capital

Who owns RUNAGAIN AS?

RUNAGAIN AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about RUNAGAIN AS

Who owns RUNAGAIN AS?

RETAIL ROOKIES AS is the largest registered owner, with 26.8%.

What is the revenue of RUNAGAIN AS?

RUNAGAIN AS had revenue of NOK 218,000 in 2025.

Where is RUNAGAIN AS based?

RUNAGAIN AS has its business address in Drammen.

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

Report a problem

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