BIZTRAC BETA
Rental and operating of own or leased real estate

UNIMATEC EIENDOM AS

Org. no. 988008826 Limited company (AS) Ålesund Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 631,000
Equity NOK 803,000
Incorporated 2005
Share capital NOK 100,000

UNIMATEC EIENDOM AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 988008826. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utvikling og utleie av nærings- og boligeiendom, samt annet som står i naturlig forbindelse med dette. Selskapet kan delta i andre selskaper med samme eller lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 631,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 631,000
Equity
NOK 803,000
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns UNIMATEC EIENDOM AS?

UNIMATEC INVEST AS
UNIMATEC EIENDOM AS
NOK 2.0m rev. · NOK 631,000 profit

UNIMATEC EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about UNIMATEC EIENDOM AS

Who owns UNIMATEC EIENDOM AS?

UNIMATEC INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of UNIMATEC EIENDOM AS?

UNIMATEC EIENDOM AS had revenue of NOK 2.0m in 2025.

Who is the general manager of UNIMATEC EIENDOM AS?

Runar Eidem is registered as general manager of UNIMATEC EIENDOM AS.

Where is UNIMATEC EIENDOM AS based?

UNIMATEC EIENDOM AS has its business address in Ålesund.

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.