biztrac. BETA
COMPANY REGISTER PROFILE
923730796 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Preparation of maps and surveying

OSLO OPPMÅLING AS

Org. no. 923730796 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 10.2m
Operating profit NOK 122,000
Equity NOK 1.3m
Incorporated 2019
Employees 10
Share capital NOK 300,000

OSLO OPPMÅLING AS is registered as a limited company in Oslo, Oslo with organisation number 923730796. The business is classified under preparation of maps and surveying (NACE 71.123). The company was incorporated in 2019 and has 10 registered employees. Registered share capital is NOK 300,000, divided into 100 shares. The company's stated purpose is: “Oppmåling- og landmålingsarbeider med dertil hørende virksomhet og deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.2m in revenue and NOK 122,000 in operating profit.

Key figures · 2025

Revenue
NOK 10.2m
▼ −9 %
Operating profit
NOK 122,000
▼ −84 %
Equity
NOK 1.3m
▲ +8 %
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
2.30
Very good
Current assets ÷ current liabilities
Profitability
3.4%
Weak
Return on total assets
Solidity
33.2%
Good
Equity as a share of total capital

Who owns OSLO OPPMÅLING AS?

OSLO OPPMÅLING AS
NOK 10.2m rev. · NOK 122,000 profit

OSLO OPPMÅLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OSLO OPPMÅLING AS

Who owns OSLO OPPMÅLING AS?

T. MARSTEIN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of OSLO OPPMÅLING AS?

OSLO OPPMÅLING AS had revenue of NOK 10.2m in 2025.

Who is the general manager of OSLO OPPMÅLING AS?

Edel Kristine Aas is registered as general manager of OSLO OPPMÅLING AS.

Where is OSLO OPPMÅLING AS based?

OSLO OPPMÅLING 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 03.10.2026.

Report a problem

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