biztrac. BETA
COMPANY REGISTER PROFILE
988896489 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

OMAGATA 118 AS

Org. no. 988896489 Limited company (AS) Kristiansund Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 652,000
Equity NOK 556,000
Incorporated 2005
Share capital NOK 556,000

OMAGATA 118 AS is registered as a limited company in Kristiansund, Møre og Romsdal with organisation number 988896489. 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 556,000, divided into 556 shares. The company's stated purpose is: “Investering i selskaper, verdipapirer, eiendom m.v.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 652,000 in operating profit.

Former names: AANDAHL & OLSEN VEKST AS, RIO EIENDOM KRISTIANSUND AS

Key figures · 2025

Revenue
NOK 1.1m
▲ +2 %
Operating profit
NOK 652,000
▲ +41 %
Equity
NOK 556,000
▼ −41 %
Est. value
NOK 940,000

Financial health · 2025

Liquidity
2.48
Very good
Current assets ÷ current liabilities
Profitability
6.8%
Satisfactory
Return on total assets
Solidity
5.6%
Weak
Equity as a share of total capital

Who owns OMAGATA 118 AS?

OMAGATA 118 AS
NOK 1.1m rev. · NOK 652,000 profit

OMAGATA 118 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OMAGATA 118 AS

Who owns OMAGATA 118 AS?

ELECTRO TEAM AS is the largest registered owner, with 100.0%.

What is the revenue of OMAGATA 118 AS?

OMAGATA 118 AS had revenue of NOK 1.1m in 2025.

Who is the general manager of OMAGATA 118 AS?

Espen Kvambe is registered as general manager of OMAGATA 118 AS.

Where is OMAGATA 118 AS based?

OMAGATA 118 AS has its business address in Kristiansund N.

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

Report a problem

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