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

BREIBUKT AS

Org. no. 989192906 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −3,000
Equity NOK 13.2m
Incorporated 2005
Share capital NOK 55,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−3k kr).

BREIBUKT AS is registered as a limited company in Oslo, Oslo with organisation number 989192906. 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 55,000, divided into 5000 shares. The company's stated purpose is: “Investeringsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −3,000
▼ −15 %
Equity
NOK 13.2m
▲ +11 %
Est. value
NOK 9.5m

Financial health · 2025

Liquidity
75.72
Very good
Current assets ÷ current liabilities
Profitability
11.2%
Good
Return on total assets
Solidity
99.0%
Very good
Equity as a share of total capital

Who owns BREIBUKT AS?

BREIBUKT AS
NOK 0 rev. · NOK −3,000 profit

BREIBUKT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BREIBUKT AS own?

BREIBUKT AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about BREIBUKT AS

Who owns BREIBUKT AS?

Geir Stormorken is the largest registered owner, with 100.0%.

What is the revenue of BREIBUKT AS?

BREIBUKT AS had revenue of NOK 0 in 2025.

Who is the general manager of BREIBUKT AS?

Geir Stormorken is registered as general manager of BREIBUKT AS.

Where is BREIBUKT AS based?

BREIBUKT 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.