BIZTRAC BETA
Civil engineering activities

BRAKON AS

Org. no. 970918701 Limited company (AS) Porsgrunn Incorporated 1994 Active
Ownership graph ↗
Revenue 2024 NOK 35.0m
Operating profit NOK −2.1m
Equity NOK 1.7m
Incorporated 1994
Employees 25
Share capital NOK 5.0m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,1 mill kr).

BRAKON AS is registered as a limited company in Porsgrunn, Telemark with organisation number 970918701. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 1994 and has 25 registered employees. Registered share capital is NOK 5.0m, divided into 10000 shares. The company's stated purpose is: “Å drive konsulentvirksomhet innen brann og sikkerhetsteknikk og å engasjere seg i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 35.0m in revenue and NOK −2.1m in operating profit.

Key figures · 2024

Revenue
NOK 35.0m
Operating profit
NOK −2.1m
Equity
NOK 1.7m
Est. value
NOK 35.8m

Financial health · 2024

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

Who owns BRAKON AS?

SUNDET INVEST AS
BRAKON AS
NOK 35.0m rev. · NOK −2.1m profit

BRAKON AS has 6 registered shareholders:

All shareholders and roles →

Which companies does BRAKON AS own?

BRAKON AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BRAKON AS

Who owns BRAKON AS?

SUNDET INVEST AS is the largest registered owner, with 76.3%.

What is the revenue of BRAKON AS?

BRAKON AS had revenue of NOK 35.0m in 2024.

Who is the general manager of BRAKON AS?

Bjørge Fredheim is registered as general manager of BRAKON AS.

Where is BRAKON AS based?

BRAKON AS has its business address in Brevik.

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.