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

NORPENSJON AS

Org. no. 930366609 Limited company (AS) Bærum Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 8.9m
Operating profit NOK 1.7m
Equity NOK 391,000
Incorporated 2022
Share capital NOK 30,000

NORPENSJON AS is registered as a limited company in Bærum, Akershus with organisation number 930366609. 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 30000 shares. The company's stated purpose is: “Konsulenttjenester/merkantile tjenester og formidling av forsikring. Selskapet kan eie aksjer/andeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.9m in revenue and NOK 1.7m in operating profit.

Former names: CAVAL CONSULTING AS

Key figures · 2025

Revenue
NOK 8.9m
▲ +241 %
Operating profit
NOK 1.7m
▲ +522 %
Equity
NOK 391,000
▲ +0 %
Est. value
NOK 6.5m

Financial health · 2025

Liquidity
1.14
Satisfactory
Current assets ÷ current liabilities
Profitability
76.1%
Very good
Return on total assets
Solidity
12.2%
Satisfactory
Equity as a share of total capital

Who owns NORPENSJON AS?

NORPENSJON AS
NOK 8.9m rev. · NOK 1.7m profit

NORPENSJON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORPENSJON AS

Who owns NORPENSJON AS?

CAVAL GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of NORPENSJON AS?

NORPENSJON AS had revenue of NOK 8.9m in 2025.

Who is the general manager of NORPENSJON AS?

Jens Aasbø Øverland is registered as general manager of NORPENSJON AS.

Where is NORPENSJON AS based?

NORPENSJON AS has its business address in Stabekk.

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.