BIZTRAC BETA
Buying and selling of own real estate

LYS PÅ VEI AS

Org. no. 993023655 Limited company (AS) Sarpsborg Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −4,000
Equity NOK −2.5m
Incorporated 2008
Share capital NOK 100,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−2,5 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4k kr).
  • Nylig endring 2026-05-11 Adresseendring registrert 2026-05-11.

LYS PÅ VEI AS is registered as a limited company in Sarpsborg, Østfold with organisation number 993023655. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Erverve, eie og selge aksjer i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −4,000
Equity
NOK −2.5m

Financial health · 2025

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

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

Who owns LYS PÅ VEI AS?

KOTAS AS
LYS PÅ VEI AS
NOK 0 rev. · NOK −4,000 profit

LYS PÅ VEI AS has 2 registered shareholders:

All shareholders and roles →

Which companies does LYS PÅ VEI AS own?

LYS PÅ VEI AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LYS PÅ VEI AS

Who owns LYS PÅ VEI AS?

KOTAS AS is the largest registered owner, with 66.0%.

What is the revenue of LYS PÅ VEI AS?

LYS PÅ VEI AS had revenue of NOK 0 in 2024.

Where is LYS PÅ VEI AS based?

LYS PÅ VEI AS has its business address in Sarpsborg.

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.