BIZTRAC BETA
Manufacture of other general-purpose machinery n.e.c.

NORDRE VIKEN AS

Org. no. 844208642 Limited company (AS) Drammen Incorporated 1987 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −18,000
Equity NOK 1.9m
Incorporated 1987
Share capital NOK 248,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−18k kr).

NORDRE VIKEN AS is registered as a limited company in Drammen, Buskerud with organisation number 844208642. The business is classified under manufacture of other general-purpose machinery n.e.c. (NACE 28.290). The company was incorporated in 1987. Registered share capital is NOK 248,000, divided into 495 shares. The company's stated purpose is: “Deltakelse i andre selskaper gjennom kjøp og salg av aksjer eller andeler. Selskapets formål omfatter også kjøp, salg og drift av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −18,000
Equity
NOK 1.9m
Est. value
NOK 2.3m

Financial health · 2024

Liquidity
105.00
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
99.1%
Very good
Equity as a share of total capital

Who owns NORDRE VIKEN AS?

JANNICKE KNUTSEN
NORDRE VIKEN AS
NOK 0 rev. · NOK −18,000 profit

NORDRE VIKEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORDRE VIKEN AS

Who owns NORDRE VIKEN AS?

JANNICKE KNUTSEN is the largest registered owner, with 100.0%.

What is the revenue of NORDRE VIKEN AS?

NORDRE VIKEN AS had revenue of NOK 0 in 2024.

Who is the general manager of NORDRE VIKEN AS?

Jannicke Knutsen is registered as general manager of NORDRE VIKEN AS.

Where is NORDRE VIKEN AS based?

NORDRE VIKEN AS has its business address in Drammen.

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.