BIZTRAC BETA
Business and other management consultancy activities

BREKKO AS

Org. no. 999294138 Limited company (AS) Øygarden Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 268,000
Operating profit NOK −36,000
Equity NOK 278,000
Incorporated 2012
Share capital NOK 30,000

Signals

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

BREKKO AS is registered as a limited company in Øygarden, Vestland with organisation number 999294138. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i andre selskap, konsulenttjenester, samt dertil hørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 268,000 in revenue and NOK −36,000 in operating profit.

Key figures · 2025

Revenue
NOK 268,000
Operating profit
NOK −36,000
Equity
NOK 278,000
Est. value
NOK 417,000

Financial health · 2025

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

Who owns BREKKO AS?

ØYSTEIN EINEVOLL TORSVIK
BREKKO AS
NOK 268,000 rev. · NOK −36,000 profit

BREKKO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BREKKO AS own?

BREKKO AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BREKKO AS

Who owns BREKKO AS?

ØYSTEIN EINEVOLL TORSVIK is the largest registered owner, with 100.0%.

What is the revenue of BREKKO AS?

BREKKO AS had revenue of NOK 268,000 in 2025.

Who is the general manager of BREKKO AS?

Øystein Einevoll Torsvik is registered as general manager of BREKKO AS.

Where is BREKKO AS based?

BREKKO AS has its business address in Rong.

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.