BIZTRAC BETA
Computer programming activities

KEYGUIDES AS

Org. no. 816996392 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 547,000
Operating profit NOK −4.6m
Equity NOK 8.9m
Incorporated 2016
Share capital NOK 1.9m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4,6 mill kr).

KEYGUIDES AS is registered as a limited company in Oslo, Oslo with organisation number 816996392. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2016. Registered share capital is NOK 1.9m, divided into 18572527 shares. The company's stated purpose is: “Elektroniske servicetjenester for turisme og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 547,000 in revenue and NOK −4.6m in operating profit.

Key figures · 2024

Revenue
NOK 547,000
Operating profit
NOK −4.6m
Equity
NOK 8.9m
Est. value
NOK 4.9m

Financial health · 2024

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

Who owns KEYGUIDES AS?

STAYER CONSULT AS
KEYGUIDES AS
NOK 547,000 rev. · NOK −4.6m profit

KEYGUIDES AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does KEYGUIDES AS own?

KEYGUIDES AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KEYGUIDES AS

Who owns KEYGUIDES AS?

STAYER CONSULT AS is the largest registered owner, with 31.4%.

What is the revenue of KEYGUIDES AS?

KEYGUIDES AS had revenue of NOK 547,000 in 2024.

Who is the general manager of KEYGUIDES AS?

Knut Michael Asplund is registered as general manager of KEYGUIDES AS.

Where is KEYGUIDES AS based?

KEYGUIDES AS has its business address in Oslo.

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.