BIZTRAC BETA
Development of building projects

VIKSEFJORDEN BRYGGE AS

Org. no. 991007415 Limited company (AS) Karmøy Incorporated 2007 Active
Ownership graph ↗
Operating profit NOK −35,000
Equity NOK −883,000
Incorporated 2007
Share capital NOK 3.6m

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−883k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−35k kr).
  • Nylig endring 2026-02-19 Aksjekapital registrert 2026-02-19.

VIKSEFJORDEN BRYGGE AS is registered as a limited company in Karmøy, Rogaland with organisation number 991007415. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2007. Registered share capital is NOK 3.6m, divided into 360000 shares. The company's stated purpose is: “Eiendomsvirksomhet som omhandler utvikling, kjøp, salg og bygging av eiendom. Videre utleievirksomhet tilknyttet dette. Selskapet kan også delta i andre virksomheter. ”.

Key figures · 2025

Operating profit
NOK −35,000
Equity
NOK −883,000

Financial health · 2025

Liquidity
89.49
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-10.5%
Weak
Equity as a share of total capital

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

Who owns VIKSEFJORDEN BRYGGE AS?

TRYGVE J. SJØEN INVESTERING AS
VIKSEFJORDEN BRYGGE AS
· NOK −35,000 profit

VIKSEFJORDEN BRYGGE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VIKSEFJORDEN BRYGGE AS

Who owns VIKSEFJORDEN BRYGGE AS?

TRYGVE J. SJØEN INVESTERING AS is the largest registered owner, with 50.0%.

Who is the general manager of VIKSEFJORDEN BRYGGE AS?

Kenneth Sjøen is registered as general manager of VIKSEFJORDEN BRYGGE AS.

Where is VIKSEFJORDEN BRYGGE AS based?

VIKSEFJORDEN BRYGGE AS has its business address in Åkrehamn.

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.