BIZTRAC BETA
Business and other management consultancy activities

ANALYSESJEFENE AS

Org. no. 929678826 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 3.0m
Operating profit NOK −58,000
Equity NOK 302,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−58k kr).

ANALYSESJEFENE AS is registered as a limited company in Oslo, Oslo with organisation number 929678826. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Datainnhenting, analyse, rådgivning og andre konsulenttjenester for å bistå selskaper med markedsføring og kommunikasjon.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.0m in revenue and NOK −58,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.0m
Operating profit
NOK −58,000
Equity
NOK 302,000
Est. value
NOK 3.3m

Financial health · 2024

Liquidity
1.24
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.4%
Good
Equity as a share of total capital

Who owns ANALYSESJEFENE AS?

CAPPEA AS
ANALYSESJEFENE AS
NOK 3.0m rev. · NOK −58,000 profit

ANALYSESJEFENE AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about ANALYSESJEFENE AS

Who owns ANALYSESJEFENE AS?

CAPPEA AS is the largest registered owner, with 92.0%.

What is the revenue of ANALYSESJEFENE AS?

ANALYSESJEFENE AS had revenue of NOK 3.0m in 2024.

Who is the general manager of ANALYSESJEFENE AS?

Caspar Aarstad Wildhagen is registered as general manager of ANALYSESJEFENE AS.

Where is ANALYSESJEFENE AS based?

ANALYSESJEFENE 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 15.06.2026.

Report a problem

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