BIZTRAC BETA
Geological surveying

GEORIGG NORWAY AS

Org. no. 929445058 Limited company (AS) Trondheim Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 6.8m
Operating profit NOK 366,000
Equity NOK 2.1m
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-04-28 Adresseendring registrert 2026-04-28.

GEORIGG NORWAY AS is registered as a limited company in Trondheim, Trøndelag with organisation number 929445058. The business is classified under geological surveying (NACE 71.122). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Levere geotekniske grunnundersøkelser og annen forretningsmessig virksomhet som anses fremmende for selskapet og dermed står i forbindelse, herunder delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.8m in revenue and NOK 366,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.8m
Operating profit
NOK 366,000
Equity
NOK 2.1m
Est. value
NOK 2.1m

Financial health · 2025

Liquidity
1.62
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
31.7%
Good
Equity as a share of total capital

Who owns GEORIGG NORWAY AS?

GLIDER HOLDING AS
GEORIGG NORWAY AS
NOK 6.8m rev. · NOK 366,000 profit

GEORIGG NORWAY AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about GEORIGG NORWAY AS

Who owns GEORIGG NORWAY AS?

GLIDER HOLDING AS is the largest registered owner, with 48.0%.

What is the revenue of GEORIGG NORWAY AS?

GEORIGG NORWAY AS had revenue of NOK 6.8m in 2025.

Who is the general manager of GEORIGG NORWAY AS?

Bernhard Rønning is registered as general manager of GEORIGG NORWAY AS.

Where is GEORIGG NORWAY AS based?

GEORIGG NORWAY AS has its business address in Trondheim.

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.