BIZTRAC BETA
Rental and operating of own or leased real estate

SYKKELHUSET EIENDOM AS

Org. no. 894729902 Limited company (AS) Levanger Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 240,000
Operating profit NOK 92,000
Equity NOK 360,000
Incorporated 2009
Share capital NOK 300,000

SYKKELHUSET EIENDOM AS is registered as a limited company in Levanger, Trøndelag with organisation number 894729902. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Eiendoms- og handelsvirksomhet og hva hermed står i forbindelse, herunder ved aksjeinnskudd eller på annen måte å delta i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 240,000 in revenue and NOK 92,000 in operating profit.

Key figures · 2025

Revenue
NOK 240,000
Operating profit
NOK 92,000
Equity
NOK 360,000
Est. value
NOK 448,000

Financial health · 2025

Liquidity
1.45
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
53.2%
Very good
Equity as a share of total capital

Who owns SYKKELHUSET EIENDOM AS?

SVERRE RØDAL
SYKKELHUSET EIENDOM AS
NOK 240,000 rev. · NOK 92,000 profit

SYKKELHUSET EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SYKKELHUSET EIENDOM AS

Who owns SYKKELHUSET EIENDOM AS?

SVERRE RØDAL is the largest registered owner, with 50.0%.

What is the revenue of SYKKELHUSET EIENDOM AS?

SYKKELHUSET EIENDOM AS had revenue of NOK 240,000 in 2025.

Who is the general manager of SYKKELHUSET EIENDOM AS?

Roar Skjei is registered as general manager of SYKKELHUSET EIENDOM AS.

Where is SYKKELHUSET EIENDOM AS based?

SYKKELHUSET EIENDOM AS has its business address in Levanger.

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.