BIZTRAC BETA
Computer programming activities

BREYTA AS

Org. no. 927668734 Limited company (AS) Bærum Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 565,000
Operating profit NOK −10.2m
Equity NOK −20.4m
Incorporated 2021
Share capital NOK 50,000

Signals

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

BREYTA AS is registered as a limited company in Bærum, Akershus with organisation number 927668734. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2021. Registered share capital is NOK 50,000, divided into 49505 shares. The company's stated purpose is: “Programmeringstjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 565,000 in revenue and NOK −10.2m in operating profit.

Key figures · 2024

Revenue
NOK 565,000
Operating profit
NOK −10.2m
Equity
NOK −20.4m

Financial health · 2024

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

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

Who owns BREYTA AS?

CMOEN INVEST AS
BREYTA AS
NOK 565,000 rev. · NOK −10.2m profit

BREYTA AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does BREYTA AS own?

BREYTA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BREYTA AS

Who owns BREYTA AS?

CMOEN INVEST AS is the largest registered owner, with 52.6%.

What is the revenue of BREYTA AS?

BREYTA AS had revenue of NOK 565,000 in 2024.

Who is the general manager of BREYTA AS?

Christoffer Moen is registered as general manager of BREYTA AS.

Where is BREYTA AS based?

BREYTA AS has its business address in Kolsås.

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.