BIZTRAC BETA
Computer programming activities

DROTTNING GEO AS

Org. no. 930124087 Limited company (AS) Bergen Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 850,000
Operating profit NOK 151,000
Equity NOK 272,000
Incorporated 2022
Share capital NOK 30,000

DROTTNING GEO AS is registered as a limited company in Bergen, Vestland with organisation number 930124087. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Tilby tjenester, formidling og programvare innen geofysikk og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 850,000 in revenue and NOK 151,000 in operating profit.

Key figures · 2025

Revenue
NOK 850,000
Operating profit
NOK 151,000
Equity
NOK 272,000
Est. value
NOK 1.0m

Financial health · 2025

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

Who owns DROTTNING GEO AS?

ÅSMUND HAUKVIK DROTTNING
DROTTNING GEO AS
NOK 850,000 rev. · NOK 151,000 profit

DROTTNING GEO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DROTTNING GEO AS own?

DROTTNING GEO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about DROTTNING GEO AS

Who owns DROTTNING GEO AS?

ÅSMUND HAUKVIK DROTTNING is the largest registered owner, with 100.0%.

What is the revenue of DROTTNING GEO AS?

DROTTNING GEO AS had revenue of NOK 850,000 in 2025.

Who is the general manager of DROTTNING GEO AS?

Åsmund Haukvik Drottning is registered as general manager of DROTTNING GEO AS.

Where is DROTTNING GEO AS based?

DROTTNING GEO AS has its business address in Ulset.

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.