biztrac. BETA
COMPANY REGISTER PROFILE
996380416 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
In liquidation UPDATED 03.10.2026
⚠FOTKLINIKKEN OLSTAD AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Other health services

FOTKLINIKKEN OLSTAD AS

Org. no. 996380416 Limited company (AS) Sogndal Incorporated 2011 In liquidation
Revenue 2025 NOK 687,000
Operating profit NOK −113,000
Equity NOK 188,000
Incorporated 2011
Share capital NOK 100,000

Signals

1 flags
  • Under avvikling Selskapet er under frivillig avvikling.

FOTKLINIKKEN OLSTAD AS is registered as a limited company in Sogndal, Vestland with organisation number 996380416. The business is classified under other health services (NACE 86.993). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Fotklinikk og anna virksomhet knyttet til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 687,000 in revenue and NOK −113,000 in operating profit.

Key figures · 2025

Revenue
NOK 687,000
▼ −3 %
Operating profit
NOK −113,000
▼ −85 %
Equity
NOK 188,000
▼ −34 %

Financial health · 2025

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

Who owns FOTKLINIKKEN OLSTAD AS?

FOTKLINIKKEN OLSTAD AS
NOK 687,000 rev. · NOK −113,000 profit

FOTKLINIKKEN OLSTAD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FOTKLINIKKEN OLSTAD AS

Who owns FOTKLINIKKEN OLSTAD AS?

Leif Olstad is the largest registered owner, with 100.0%.

What is the revenue of FOTKLINIKKEN OLSTAD AS?

FOTKLINIKKEN OLSTAD AS had revenue of NOK 687,000 in 2025.

Where is FOTKLINIKKEN OLSTAD AS based?

FOTKLINIKKEN OLSTAD AS has its business address in Sogndal.

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.