BIZTRAC BETA
Wholesale of mining, construction and civil engineering machinery

GEOSAFE AS

Org. no. 933023214 Limited company (AS) Trondheim Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 73.6m
Operating profit NOK 3.7m
Equity NOK 17.5m
Incorporated 2024
Employees 9
Share capital NOK 120,000

Signals

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

GEOSAFE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 933023214. The business is classified under wholesale of mining, construction and civil engineering machinery (NACE 46.630). The company was incorporated in 2024 and has 9 registered employees. Registered share capital is NOK 120,000, divided into 600 shares. The company's stated purpose is: “Markedsføring, handel og service, samt hva som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 73.6m in revenue and NOK 3.7m in operating profit.

Key figures · 2024

Revenue
NOK 73.6m
Operating profit
NOK 3.7m
Equity
NOK 17.5m
Est. value
NOK 23.5m

Financial health · 2025

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

Who owns GEOSAFE AS?

GEOSAFE HOLDING AS
GEOSAFE AS
NOK 73.6m rev. · NOK 3.7m profit

GEOSAFE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GEOSAFE AS

Who owns GEOSAFE AS?

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

What is the revenue of GEOSAFE AS?

GEOSAFE AS had revenue of NOK 73.6m in 2024.

Who is the general manager of GEOSAFE AS?

Rune Austad Handberg is registered as general manager of GEOSAFE AS.

Where is GEOSAFE AS based?

GEOSAFE AS has its business address in Tiller.

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.