BIZTRAC BETA
Preparation of maps and surveying

SKARTUM OPPMÅLING AS

Org. no. 922063273 Limited company (AS) Sigdal Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 7.9m
Operating profit NOK 595,000
Equity NOK 3.3m
Incorporated 2019
Share capital NOK 210,000

SKARTUM OPPMÅLING AS is registered as a limited company in Sigdal, Buskerud with organisation number 922063273. The business is classified under preparation of maps and surveying (NACE 71.123). The company was incorporated in 2019. Registered share capital is NOK 210,000, divided into 100 shares. The company's stated purpose is: “Utføre kart- og oppmålingstjenester, konsulentvirksomhet og annen virksomhet som naturlig faller inn under dette. Salg av varer/tjenester relatert til anleggsbransjen/jord og skogbruk.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.9m in revenue and NOK 595,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.9m
Operating profit
NOK 595,000
Equity
NOK 3.3m
Est. value
NOK 4.9m

Financial health · 2024

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

Who owns SKARTUM OPPMÅLING AS?

SKARTUM HOLDING AS
SKARTUM OPPMÅLING AS
NOK 7.9m rev. · NOK 595,000 profit

SKARTUM OPPMÅLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SKARTUM OPPMÅLING AS

Who owns SKARTUM OPPMÅLING AS?

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

What is the revenue of SKARTUM OPPMÅLING AS?

SKARTUM OPPMÅLING AS had revenue of NOK 7.9m in 2024.

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

Andreas Skartum is registered as general manager of SKARTUM OPPMÅLING AS.

Where is SKARTUM OPPMÅLING AS based?

SKARTUM OPPMÅLING AS has its business address in Prestfoss.

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.