BIZTRAC BETA
Rental and operating of own or leased real estate

ETHO AS

Org. no. 990385629 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 3,000
Operating profit NOK −923,000
Equity NOK 269.4m
Incorporated 2006
Share capital NOK 350,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−923k kr).

ETHO AS is registered as a limited company in Oslo, Oslo with organisation number 990385629. 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 350,000, divided into 350 shares. The company's stated purpose is: “Selskapets virksomhet er investeringer, herunder egen investering i verdipapirer, låneinstrumenter og gjeldsbrev, fast eiendom og kapitalvarer, samt enhver virksomhet som står i forbindelse med dette, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 3,000 in revenue and NOK −923,000 in operating profit.

Key figures · 2024

Revenue
NOK 3,000
Operating profit
NOK −923,000
Equity
NOK 269.4m
Est. value
NOK 403.7m

Financial health · 2024

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

Who owns ETHO AS?

TROND HORNELAND
ETHO AS
NOK 3,000 rev. · NOK −923,000 profit

ETHO AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ETHO AS own?

ETHO AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ETHO AS

Who owns ETHO AS?

TROND HORNELAND is the largest registered owner, with 90.0%.

What is the revenue of ETHO AS?

ETHO AS had revenue of NOK 3,000 in 2024.

Where is ETHO AS based?

ETHO AS has its business address in Oslo.

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.