biztrac. BETA
COMPANY REGISTER PROFILE
934920724 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Construction of utility projects for fluids

LANGØYBRUA AS

Org. no. 934920724 Limited company (AS) Kragerø Incorporated 1983 Active
Operating profit NOK −5,000
Equity NOK −21,000
Incorporated 1983
Share capital NOK 220,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−21k kr).

LANGØYBRUA AS is registered as a limited company in Kragerø, Telemark with organisation number 934920724. The business is classified under construction of utility projects for fluids (NACE 42.210). The company was incorporated in 1983. Registered share capital is NOK 220,000. The company's stated purpose is: “Ideelt aksjeselskap med formål å bidra til bygging og eventuell drift av bru til Langøy i Kragerø kommune, samt delta i bygging og drift av Langøyveien og fremtidig forbindelse til Gumøy. Dette i et aktivt samarbeid med private og offentlige virksomheter.”.

Key figures · 2025

Operating profit
NOK −5,000
▼ −7 %
Equity
NOK −21,000
▼ −31 %

Financial health · 2025

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-12534.1%
Weak
Equity as a share of total capital

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

Who owns LANGØYBRUA AS?

LANGØYBRUA AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does LANGØYBRUA AS own?

LANGØYBRUA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LANGØYBRUA AS

Who owns LANGØYBRUA AS?

LANGØYBRUA AS is the largest registered owner, with 53.2%.

Who is the general manager of LANGØYBRUA AS?

Christian Wiik is registered as general manager of LANGØYBRUA AS.

Where is LANGØYBRUA AS based?

LANGØYBRUA AS has its business address in Kragerø Skjærgård.

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.