BIZTRAC BETA
Development of building projects

VIKEN GRUNNUTVIKLING AS

Org. no. 928710815 Limited company (AS) Fredrikstad Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −17,000
Equity NOK −101,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−101k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−17k kr).

VIKEN GRUNNUTVIKLING AS is registered as a limited company in Fredrikstad, Østfold with organisation number 928710815. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp, salg, utvikling og utleie av fast eiendom, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −17,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −17,000
Equity
NOK −101,000

Financial health · 2025

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

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

Who owns VIKEN GRUNNUTVIKLING AS?

BYGGMESTER TOR E JOHANSEN AS
VIKEN GRUNNUTVIKLING AS
NOK 0 rev. · NOK −17,000 profit

VIKEN GRUNNUTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VIKEN GRUNNUTVIKLING AS

Who owns VIKEN GRUNNUTVIKLING AS?

BYGGMESTER TOR E JOHANSEN AS is the largest registered owner, with 100.0%.

What is the revenue of VIKEN GRUNNUTVIKLING AS?

VIKEN GRUNNUTVIKLING AS had revenue of NOK 0 in 2024.

Where is VIKEN GRUNNUTVIKLING AS based?

VIKEN GRUNNUTVIKLING AS has its business address in Gressvik.

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.