biztrac. BETA
COMPANY REGISTER PROFILE
932040948 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Civil engineering activities

TOPOGRAF AS

Org. no. 932040948 Limited company (AS) Skien Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 51,000
Equity NOK 219,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TOPOGRAF AS is registered as a limited company in Skien, Telemark with organisation number 932040948. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Konsulenttjenester innen eiendom, bygg og oppmåling.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 51,000 in operating profit.

Former names: EIENDOM, BYGG OG OPPMÅLING AS, HEIMSKOGEN CONSULTING AS

Key figures · 2025

Revenue
NOK 2.6m
▲ +139 %
Operating profit
NOK 51,000
▼ −81 %
Equity
NOK 219,000
▲ +18 %
Est. value
NOK 709,000

Financial health · 2025

Liquidity
1.12
Satisfactory
Current assets ÷ current liabilities
Profitability
4.8%
Weak
Return on total assets
Solidity
20.3%
Good
Equity as a share of total capital

Who owns TOPOGRAF AS?

TOPOGRAF AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about TOPOGRAF AS

Who owns TOPOGRAF AS?

PLAN OG EIENDOM AS is the largest registered owner, with 80.0%.

What is the revenue of TOPOGRAF AS?

TOPOGRAF AS had revenue of NOK 2.6m in 2025.

Who is the general manager of TOPOGRAF AS?

Robert Bergan is registered as general manager of TOPOGRAF AS.

Where is TOPOGRAF AS based?

TOPOGRAF AS has its business address in Skien.

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.