BIZTRAC BETA
Uoppgitt

LYSNE BYGG & EIENDOM AS

Org. no. 932128055 Limited company (AS) Ås Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 210,000
Operating profit NOK −48,000
Equity NOK −342,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−342k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−48k kr).

LYSNE BYGG & EIENDOM AS is registered as a limited company in Ås, Akershus with organisation number 932128055. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investering i aksjer, andeler og obligasjoner, investering i og drift av eiendom, investering i andre investeringsobjekter samt konsulentvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 210,000 in revenue and NOK −48,000 in operating profit.

Key figures · 2025

Revenue
NOK 210,000
Operating profit
NOK −48,000
Equity
NOK −342,000

Financial health · 2025

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

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

Who owns LYSNE BYGG & EIENDOM AS?

EKEH AS
LYSNE BYGG & EIENDOM AS
NOK 210,000 rev. · NOK −48,000 profit

LYSNE BYGG & EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LYSNE BYGG & EIENDOM AS

Who owns LYSNE BYGG & EIENDOM AS?

EKEH AS is the largest registered owner, with 50.0%.

What is the revenue of LYSNE BYGG & EIENDOM AS?

LYSNE BYGG & EIENDOM AS had revenue of NOK 210,000 in 2025.

Where is LYSNE BYGG & EIENDOM AS based?

LYSNE BYGG & EIENDOM AS has its business address in Vinterbro.

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.