biztrac. BETA
COMPANY REGISTER PROFILE
914951852 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Computer programming activities

FORSE AS

Org. no. 914951852 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 108.2m
Operating profit NOK 20.2m
Equity NOK 4.6m
Incorporated 2014
Employees 44
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-07-23 Adresseendring registrert 2026-07-23.

FORSE AS is registered as a limited company in Oslo, Oslo with organisation number 914951852. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2014 and has 44 registered employees. Registered share capital is NOK 30,000, divided into 100000 shares. The company's stated purpose is: “Levering av konsulenttjenester og tjenester innen programvareutvikling. Samt det som naturlig følger av dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 108.2m in revenue and NOK 20.2m in operating profit.

Former names: FORSE.NET AS

Key figures · 2025

Revenue
NOK 108.2m
▲ +14 %
Operating profit
NOK 20.2m
▲ +24 %
Equity
NOK 4.6m
▲ +21 %
Est. value
NOK 115.7m

Financial health · 2025

Liquidity
1.09
Satisfactory
Current assets ÷ current liabilities
Profitability
47.2%
Very good
Return on total assets
Solidity
9.4%
Weak
Equity as a share of total capital

Who owns FORSE AS?

FORSE AS
NOK 108.2m rev. · NOK 20.2m profit

FORSE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FORSE AS

Who owns FORSE AS?

INIVA GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of FORSE AS?

FORSE AS had revenue of NOK 108.2m in 2025.

Who is the general manager of FORSE AS?

Terje Andersen is registered as general manager of FORSE AS.

Where is FORSE AS based?

FORSE 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.