BIZTRAC BETA
Rental and operating of own or leased real estate

NORDLYSVEGEN 2 AS

Org. no. 989405640 Limited company (AS) Stavanger Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 2.5m
Operating profit NOK 2.1m
Equity NOK 8.2m
Incorporated 2006
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

NORDLYSVEGEN 2 AS is registered as a limited company in Stavanger, Rogaland with organisation number 989405640. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Investering i eiendom, rådgivning og deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.5m in revenue and NOK 2.1m in operating profit.

Key figures · 2024

Revenue
NOK 2.5m
Operating profit
NOK 2.1m
Equity
NOK 8.2m
Est. value
NOK 10.0m

Financial health · 2024

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

Who owns NORDLYSVEGEN 2 AS?

BERBU AS
NORDLYSVEGEN 2 AS
NOK 2.5m rev. · NOK 2.1m profit

NORDLYSVEGEN 2 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORDLYSVEGEN 2 AS

Who owns NORDLYSVEGEN 2 AS?

BERBU AS is the largest registered owner, with 100.0%.

What is the revenue of NORDLYSVEGEN 2 AS?

NORDLYSVEGEN 2 AS had revenue of NOK 2.5m in 2024.

Who is the general manager of NORDLYSVEGEN 2 AS?

Arne Johan Endresen is registered as general manager of NORDLYSVEGEN 2 AS.

Where is NORDLYSVEGEN 2 AS based?

NORDLYSVEGEN 2 AS has its business address in Stavanger.

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.