BIZTRAC BETA
Business and other management consultancy activities

MATAE BERGEN AS

Org. no. 931695339 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 7.2m
Operating profit NOK −1.8m
Equity NOK −1.8m
Incorporated 2023
Employees 9
Share capital NOK 100,000

Signals

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

MATAE BERGEN AS is registered as a limited company in Bergen, Vestland with organisation number 931695339. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2023 and has 9 registered employees. Registered share capital is NOK 100,000, divided into 10000 shares. The company's stated purpose is: “Lederrekruttering og ledergruppeevaluering. Styreevaluering og styrerekruttering. Strategisk rådgivning.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.2m in revenue and NOK −1.8m in operating profit.

Key figures · 2024

Revenue
NOK 7.2m
Operating profit
NOK −1.8m
Equity
NOK −1.8m

Financial health · 2024

Liquidity
1.09
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-89.0%
Weak
Equity as a share of total capital

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

Who owns MATAE BERGEN AS?

HEROD AS
MATAE BERGEN AS
NOK 7.2m rev. · NOK −1.8m profit

MATAE BERGEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MATAE BERGEN AS

Who owns MATAE BERGEN AS?

HEROD AS is the largest registered owner, with 90.0%.

What is the revenue of MATAE BERGEN AS?

MATAE BERGEN AS had revenue of NOK 7.2m in 2024.

Where is MATAE BERGEN AS based?

MATAE BERGEN AS has its business address in Bergen.

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.