BIZTRAC BETA
Rental and operating of own or leased real estate

BYÅSVEIEN 158 EIENDOM AS

Org. no. 920875823 Limited company (AS) Trondheim Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 2.5m
Operating profit NOK 1.9m
Equity NOK 13.7m
Incorporated 2018
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.

BYÅSVEIEN 158 EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 920875823. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 1 shares. The company's stated purpose is: “Utvikling, forvaltning og salg av fast eiendom og annen virksomhet som er beslektet med denne.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.5m in revenue and NOK 1.9m in operating profit.

Key figures · 2024

Revenue
NOK 2.5m
Operating profit
NOK 1.9m
Equity
NOK 13.7m
Est. value
NOK 13.1m

Financial health · 2024

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

Who owns BYÅSVEIEN 158 EIENDOM AS?

I K LYKKE EIENDOM HOLDING AS
BYÅSVEIEN 158 EIENDOM AS
NOK 2.5m rev. · NOK 1.9m profit

BYÅSVEIEN 158 EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BYÅSVEIEN 158 EIENDOM AS

Who owns BYÅSVEIEN 158 EIENDOM AS?

I K LYKKE EIENDOM HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BYÅSVEIEN 158 EIENDOM AS?

BYÅSVEIEN 158 EIENDOM AS had revenue of NOK 2.5m in 2024.

Where is BYÅSVEIEN 158 EIENDOM AS based?

BYÅSVEIEN 158 EIENDOM AS has its business address in Trondheim.

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.