biztrac. BETA
COMPANY REGISTER PROFILE
929022661 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Activities of orthopedists and chiropodists

FOKUSFOTEN AS

Org. no. 929022661 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 3.1m
Operating profit NOK 346,000
Equity NOK 396,000
Incorporated 2022
Share capital NOK 30,000

FOKUSFOTEN AS is registered as a limited company in Oslo, Oslo with organisation number 929022661. The business is classified under activities of orthopedists and chiropodists (NACE 86.991). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Fotterapi med såletilpassing og behandlinger, undervisning i fotterapi og ortopediteknikk, samt å eie aksjer og andeler i andre selskaper og alt som hører herunder.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK 346,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
▲ +14 %
Operating profit
NOK 346,000
▲ +115 %
Equity
NOK 396,000
▲ +199 %
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
1.48
Satisfactory
Current assets ÷ current liabilities
Profitability
46.3%
Very good
Return on total assets
Solidity
40.4%
Very good
Equity as a share of total capital

Who owns FOKUSFOTEN AS?

FOKUSFOTEN AS
NOK 3.1m rev. · NOK 346,000 profit

FOKUSFOTEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FOKUSFOTEN AS

Who owns FOKUSFOTEN AS?

Ulrikke Jonassen is the largest registered owner, with 100.0%.

What is the revenue of FOKUSFOTEN AS?

FOKUSFOTEN AS had revenue of NOK 3.1m in 2025.

Who is the general manager of FOKUSFOTEN AS?

Ulrikke Jonassen is registered as general manager of FOKUSFOTEN AS.

Where is FOKUSFOTEN AS based?

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