BIZTRAC BETA
Computer consultancy and computer facilities management activities

FOKUS DIREKTE AS

Org. no. 986708405 Limited company (AS) Fredrikstad Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 23.5m
Operating profit NOK 2.4m
Equity NOK 2.3m
Incorporated 2004
Employees 8
Share capital NOK 100,000

FOKUS DIREKTE AS is registered as a limited company in Fredrikstad, Østfold with organisation number 986708405. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2004 and has 8 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift og utvikling av internett tjenester, salg av produkter tilhørende dette, konsulenttjenester, utleie av lydutstyr, kjøp, salg, import og eksport av varer, kjøp, salg og besittelse av aksjer, å engasjere seg i beslektede virksomheter, samt alt hva som hermed måtte stå i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 23.5m in revenue and NOK 2.4m in operating profit.

Key figures · 2024

Revenue
NOK 23.5m
Operating profit
NOK 2.4m
Equity
NOK 2.3m
Est. value
NOK 14.7m

Financial health · 2024

Liquidity
1.71
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.6%
Good
Equity as a share of total capital

Who owns FOKUS DIREKTE AS?

FO-KUS AS
FOKUS DIREKTE AS
NOK 23.5m rev. · NOK 2.4m profit

FOKUS DIREKTE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FOKUS DIREKTE AS

Who owns FOKUS DIREKTE AS?

FO-KUS AS is the largest registered owner, with 50.0%.

What is the revenue of FOKUS DIREKTE AS?

FOKUS DIREKTE AS had revenue of NOK 23.5m in 2024.

Where is FOKUS DIREKTE AS based?

FOKUS DIREKTE AS has its business address in Gamle Fredrikstad.

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.