BIZTRAC BETA
Computer consultancy and computer facilities management activities

FORNOST AS

Org. no. 999093760 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 4.8m
Operating profit NOK 1.6m
Equity NOK 8.0m
Incorporated 2012
Share capital NOK 210,000

FORNOST AS is registered as a limited company in Oslo, Oslo with organisation number 999093760. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2012. Registered share capital is NOK 210,000, divided into 200000 shares. The company's stated purpose is: “Handels-, service- og konsulentvirksomhet innen IT-bransjen, investeringsvirksomhet og deltagelse i andre virksomheter, samt virksomhet knyttet til det foranstående.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.8m in revenue and NOK 1.6m in operating profit.

Key figures · 2024

Revenue
NOK 4.8m
Operating profit
NOK 1.6m
Equity
NOK 8.0m
Est. value
NOK 11.5m

Financial health · 2024

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

Who owns FORNOST AS?

GEIR EGIL MYHRE
FORNOST AS
NOK 4.8m rev. · NOK 1.6m profit

FORNOST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FORNOST AS own?

FORNOST AS holds stakes in 12 companies:

See the full ownership structure →

Frequently asked questions about FORNOST AS

Who owns FORNOST AS?

GEIR EGIL MYHRE is the largest registered owner, with 100.0%.

What is the revenue of FORNOST AS?

FORNOST AS had revenue of NOK 4.8m in 2024.

Who is the general manager of FORNOST AS?

Geir Egil Myhre is registered as general manager of FORNOST AS.

Where is FORNOST AS based?

FORNOST 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.