BIZTRAC BETA
Rental and operating of own or leased real estate

NJÅLSVEG 2 AS

Org. no. 922987726 Limited company (AS) Porsgrunn Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 144,000
Operating profit NOK −10,000
Equity NOK −2.0m
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−2,0 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−10k kr).

NJÅLSVEG 2 AS is registered as a limited company in Porsgrunn, Telemark with organisation number 922987726. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eie, drift og utleie av fast eiendom, eie aksjer i andre selskap, samt virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 144,000 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 144,000
Operating profit
NOK −10,000
Equity
NOK −2.0m

Financial health · 2025

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

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

Who owns NJÅLSVEG 2 AS?

AUTOSTRADA GRUPPEN AS
NJÅLSVEG 2 AS
NOK 144,000 rev. · NOK −10,000 profit

NJÅLSVEG 2 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NJÅLSVEG 2 AS

Who owns NJÅLSVEG 2 AS?

AUTOSTRADA GRUPPEN AS is the largest registered owner, with 50.0%.

What is the revenue of NJÅLSVEG 2 AS?

NJÅLSVEG 2 AS had revenue of NOK 144,000 in 2025.

Where is NJÅLSVEG 2 AS based?

NJÅLSVEG 2 AS has its business address in Porsgrunn.

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.