BIZTRAC BETA
COMPANY REGISTER PROFILE
913665376 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

ITO EIENDOM AS

Org. no. 913665376 Limited company (AS) Ringerike Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK 894,000
Equity NOK 9.1m
Incorporated 2014
Share capital NOK 356,000

Signals

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

ITO EIENDOM AS is registered as a limited company in Ringerike, Buskerud with organisation number 913665376. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 356,000, divided into 35577 shares. The company's stated purpose is: “Investering og drift av fast eiendom samt alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK 894,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
▲ +15 %
Operating profit
NOK 894,000
▼ −24 %
Equity
NOK 9.1m
▲ +8 %
Est. value
NOK 9.0m

Financial health · 2025

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

Who owns ITO EIENDOM AS?

ITO EIENDOM AS
NOK 2.3m rev. · NOK 894,000 profit

ITO EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ITO EIENDOM AS

Who owns ITO EIENDOM AS?

HAGESTUBB AS is the largest registered owner, with 100.0%.

What is the revenue of ITO EIENDOM AS?

ITO EIENDOM AS had revenue of NOK 2.3m in 2025.

Where is ITO EIENDOM AS based?

ITO EIENDOM AS has its business address in Tyristrand.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.