BIZTRAC BETA
Geological surveying

PROPOINT SURVEY AS

Org. no. 988912859 Limited company (AS) Bærum Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 23.4m
Operating profit NOK 1.7m
Equity NOK 5.9m
Incorporated 2005
Employees 16
Share capital NOK 100,000

PROPOINT SURVEY AS is registered as a limited company in Bærum, Akershus with organisation number 988912859. The business is classified under geological surveying (NACE 71.122). The company was incorporated in 2005 and has 16 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Stiknings- og oppmålingstjenester, investering i aksjer, deltakelse i andre selskap, samt alt hva som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 23.4m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 23.4m
Operating profit
NOK 1.7m
Equity
NOK 5.9m
Est. value
NOK 12.1m

Financial health · 2024

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

Who owns PROPOINT SURVEY AS?

HABTO HOLDING AS
PROPOINT SURVEY AS
NOK 23.4m rev. · NOK 1.7m profit

PROPOINT SURVEY AS has 2 registered shareholders:

All shareholders and roles →

Group structure

PROPOINT SURVEY AS er morselskap for 40 datterselskaper:

Frequently asked questions about PROPOINT SURVEY AS

Who owns PROPOINT SURVEY AS?

HABTO HOLDING AS is the largest registered owner, with 51.0%.

What is the revenue of PROPOINT SURVEY AS?

PROPOINT SURVEY AS had revenue of NOK 23.4m in 2024.

Who is the general manager of PROPOINT SURVEY AS?

Steinar Juvland is registered as general manager of PROPOINT SURVEY AS.

Where is PROPOINT SURVEY AS based?

PROPOINT SURVEY AS has its business address in Lysaker.

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.