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

JORUNN'S FOTKLINIKK AS

Org. no. 935080436 Limited company (AS) Larvik Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 259,000
Operating profit NOK 16,000
Equity NOK 41,000
Incorporated 2025
Share capital NOK 30,000

JORUNN'S FOTKLINIKK AS is registered as a limited company in Larvik, Vestfold with organisation number 935080436. The business is classified under activities of orthopedists and chiropodists (NACE 86.991). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Profesjonell fotbehandling med fokus på å hjelpe pasienter med ulike fotproblemer, spesielt med fokus på biomekanikk og sko.”. The most recent filed accounts, for the 2025 financial year, show NOK 259,000 in revenue and NOK 16,000 in operating profit.

Key figures · 2025

Revenue
NOK 259,000
Operating profit
NOK 16,000
Equity
NOK 41,000
Est. value
NOK 84,000

Financial health · 2025

Liquidity
10.05
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
34.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns JORUNN'S FOTKLINIKK AS?

JORUNN'S FOTKLINIKK AS
NOK 259,000 rev. · NOK 16,000 profit

JORUNN'S FOTKLINIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JORUNN'S FOTKLINIKK AS

Who owns JORUNN'S FOTKLINIKK AS?

Jorunn Brekka-Johnson is the largest registered owner, with 100.0%.

What is the revenue of JORUNN'S FOTKLINIKK AS?

JORUNN'S FOTKLINIKK AS had revenue of NOK 259,000 in 2025.

Where is JORUNN'S FOTKLINIKK AS based?

JORUNN'S FOTKLINIKK AS has its business address in Stavern.

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.