BIZTRAC BETA
Computer programming activities

FIKEN AS

Org. no. 913312465 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 464.2m
Operating profit NOK 282.8m
Equity NOK 2.7m
Incorporated 2014
Employees 87
Share capital NOK 30,000

FIKEN AS is registered as a limited company in Oslo, Oslo with organisation number 913312465. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2014 and has 87 registered employees. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Videreutvikling, markedsføring og salg av Fiken regnskapsprogram, utvikling og salg av andre dataprogrammer med tilhørende tjenester, konsulentvirksomhet innenfor IKT og annen virksomhet som faller naturlig innunder de nevnte områder.”. The most recent filed accounts, for the 2025 financial year, show NOK 464.2m in revenue and NOK 282.8m in operating profit.

Key figures · 2025

Revenue
NOK 464.2m
Operating profit
NOK 282.8m
Equity
NOK 2.7m
Est. value
NOK 853.9m

Financial health · 2025

Liquidity
0.90
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.6%
Not satisfactory
Equity as a share of total capital

Who owns FIKEN AS?

ABLOM AS
FIKEN AS
NOK 464.2m rev. · NOK 282.8m profit

FIKEN AS has 3 registered shareholders:

All shareholders and roles →

Which companies does FIKEN AS own?

FIKEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FIKEN AS

Who owns FIKEN AS?

ABLOM AS is the largest registered owner, with 33.3%.

What is the revenue of FIKEN AS?

FIKEN AS had revenue of NOK 464.2m in 2025.

Who is the general manager of FIKEN AS?

Bendik Gill Bakken is registered as general manager of FIKEN AS.

Where is FIKEN AS based?

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