biztrac. BETA
COMPANY REGISTER PROFILE
988387460 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

AREPO AS

Org. no. 988387460 Limited company (AS) Oslo Incorporated 2005 Active
Revenue 2025 NOK 144.2m
Operating profit NOK 91.6m
Equity NOK 770.5m
Incorporated 2005
Share capital NOK 500,000

AREPO AS is registered as a limited company in Oslo, Oslo with organisation number 988387460. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2005. Registered share capital is NOK 500,000, divided into 1000 shares. The company's stated purpose is: “Selskapets virksomhet skal omfatte handel, investering i fast eiendom og verdipapirer samt annen virksomhet i tilknytning til dette, herunder deltagelse i andre selskaper med tilsvarende virksomhet gjennom egenkapital, lån eller ved avgivelse av garantier.”. The most recent filed accounts, for the 2025 financial year, show NOK 144.2m in revenue and NOK 91.6m in operating profit.

Former names: STARTUP 51 AS

Key figures · 2025

Revenue
NOK 144.2m
▲ +122 %
Operating profit
NOK 91.6m
▲ +166 %
Equity
NOK 770.5m
▲ +18 %
Est. value
NOK 719.8m

Financial health · 2025

Liquidity
11.14
Very good
Current assets ÷ current liabilities
Profitability
14.9%
Good
Return on total assets
Solidity
91.1%
Very good
Equity as a share of total capital

Who owns AREPO AS?

AREPO AS has 4 registered shareholders:

All shareholders and roles →

Which companies does AREPO AS own?

AREPO AS holds stakes in 38 companies:

See the full ownership structure →

Frequently asked questions about AREPO AS

Who owns AREPO AS?

Kari Stautland is the largest registered owner, with 52.0%.

What is the revenue of AREPO AS?

AREPO AS had revenue of NOK 144.2m in 2025.

Where is AREPO AS based?

AREPO AS has its business address in Oslo.

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.