BIZTRAC BETA
Rental and operating of own or leased real estate

ELVEVEIEN 36 AS

Org. no. 998467527 Limited company (AS) Karmøy Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 3.7m
Operating profit NOK 2.0m
Equity NOK 6.9m
Incorporated 2012
Share capital NOK 30,000

Signals

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

ELVEVEIEN 36 AS is registered as a limited company in Karmøy, Rogaland with organisation number 998467527. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.7m in revenue and NOK 2.0m in operating profit.

Key figures · 2024

Revenue
NOK 3.7m
Operating profit
NOK 2.0m
Equity
NOK 6.9m
Est. value
NOK 9.1m

Financial health · 2024

Liquidity
0.02
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
38.2%
Good
Equity as a share of total capital

Who owns ELVEVEIEN 36 AS?

JH2 EIENDOM AS
ELVEVEIEN 36 AS
NOK 3.7m rev. · NOK 2.0m profit

ELVEVEIEN 36 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ELVEVEIEN 36 AS

Who owns ELVEVEIEN 36 AS?

JH2 EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of ELVEVEIEN 36 AS?

ELVEVEIEN 36 AS had revenue of NOK 3.7m in 2024.

Who is the general manager of ELVEVEIEN 36 AS?

John Feddersen Heggelund is registered as general manager of ELVEVEIEN 36 AS.

Where is ELVEVEIEN 36 AS based?

ELVEVEIEN 36 AS has its business address in Karmsund.

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.