BIZTRAC BETA
Rental and operating of own or leased real estate

ETNE 1 EIENDOM AS

Org. no. 990088306 Limited company (AS) Haugesund Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK 1.1m
Equity NOK 7.2m
Incorporated 2006
Share capital NOK 200,000

Signals

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

ETNE 1 EIENDOM AS is registered as a limited company in Haugesund, Rogaland with organisation number 990088306. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 200,000, divided into 1000 shares. The company's stated purpose is: “Eiendomsinvestering, herunder investering i og utleie av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK 1.1m
Equity
NOK 7.2m
Est. value
NOK 7.7m

Financial health · 2024

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

Who owns ETNE 1 EIENDOM AS?

HAUGLI EIENDOM AS
ETNE 1 EIENDOM AS
NOK 1.6m rev. · NOK 1.1m profit

ETNE 1 EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ETNE 1 EIENDOM AS

Who owns ETNE 1 EIENDOM AS?

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

What is the revenue of ETNE 1 EIENDOM AS?

ETNE 1 EIENDOM AS had revenue of NOK 1.6m in 2024.

Who is the general manager of ETNE 1 EIENDOM AS?

Tor-Einar Sandvik is registered as general manager of ETNE 1 EIENDOM AS.

Where is ETNE 1 EIENDOM AS based?

ETNE 1 EIENDOM AS has its business address in Haugesund.

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.