BIZTRAC BETA
Other specialised construction activities in construction of buildings

RUNE BREKKA AS

Org. no. 911673169 Limited company (AS) Kragerø Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 16.3m
Operating profit NOK 698,000
Equity NOK 3.0m
Incorporated 2013
Employees 22
Share capital NOK 30,000

RUNE BREKKA AS is registered as a limited company in Kragerø, Telemark with organisation number 911673169. The business is classified under other specialised construction activities in construction of buildings (NACE 43.420). The company was incorporated in 2013 and has 22 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Håndverktjenester innen bygg og anlegg samt annet som i den forbindelse er naturlig.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.3m in revenue and NOK 698,000 in operating profit.

Key figures · 2024

Revenue
NOK 16.3m
Operating profit
NOK 698,000
Equity
NOK 3.0m
Est. value
NOK 3.4m

Financial health · 2024

Liquidity
1.43
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.9%
Good
Equity as a share of total capital

Who owns RUNE BREKKA AS?

KONTRABASS HOLDING AS
RUNE BREKKA AS
NOK 16.3m rev. · NOK 698,000 profit

RUNE BREKKA AS has 1 registered shareholder:

All shareholders and roles →

Group structure

RUNE BREKKA AS er morselskap for 1 datterselskap:

Frequently asked questions about RUNE BREKKA AS

Who owns RUNE BREKKA AS?

KONTRABASS HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of RUNE BREKKA AS?

RUNE BREKKA AS had revenue of NOK 16.3m in 2024.

Who is the general manager of RUNE BREKKA AS?

Rune Brekka is registered as general manager of RUNE BREKKA AS.

Where is RUNE BREKKA AS based?

RUNE BREKKA AS has its business address in Kragerø.

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.