BIZTRAC BETA
Rental and operating of own or leased real estate

ACO UTLEIE AS

Org. no. 918179151 Limited company (AS) Haram Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK −1.0m
Equity NOK 2.9m
Incorporated 2016
Share capital NOK 81,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,0 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ACO UTLEIE AS is registered as a limited company in Haram, Møre og Romsdal with organisation number 918179151. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 81,000, divided into 81257 shares. The company's stated purpose is: “Eie og leie ut fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK −1.0m in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
Operating profit
NOK −1.0m
Equity
NOK 2.9m
Est. value
NOK 5.5m

Financial health · 2024

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

Who owns ACO UTLEIE AS?

ACO MØRE HOLDING AS
ACO UTLEIE AS
NOK 2.7m rev. · NOK −1.0m profit

ACO UTLEIE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ACO UTLEIE AS

Who owns ACO UTLEIE AS?

ACO MØRE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ACO UTLEIE AS?

ACO UTLEIE AS had revenue of NOK 2.7m in 2025.

Who is the general manager of ACO UTLEIE AS?

Tarjei Solbakken Rødset is registered as general manager of ACO UTLEIE AS.

Where is ACO UTLEIE AS based?

ACO UTLEIE AS has its business address in Tennfjord.

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.