BIZTRAC BETA
Rental and operating of own or leased real estate

NARVIK FYSIOTERAPI OG FOTKLINIKK AS

Org. no. 998682363 Limited company (AS) Narvik Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 739,000
Operating profit NOK 232,000
Equity NOK 609,000
Incorporated 2012
Share capital NOK 40,000

NARVIK FYSIOTERAPI OG FOTKLINIKK AS is registered as a limited company in Narvik, Nordland with organisation number 998682363. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 40,000, divided into 400 shares. The company's stated purpose is: “Å investere i og drifte fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 739,000 in revenue and NOK 232,000 in operating profit.

Key figures · 2025

Revenue
NOK 739,000
Operating profit
NOK 232,000
Equity
NOK 609,000
Est. value
NOK 838,000

Financial health · 2025

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

Who owns NARVIK FYSIOTERAPI OG FOTKLINIKK AS?

NINA HAUG VANEM
NARVIK FYSIOTERAPI OG FOTKLINIKK AS
NOK 739,000 rev. · NOK 232,000 profit

NARVIK FYSIOTERAPI OG FOTKLINIKK AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about NARVIK FYSIOTERAPI OG FOTKLINIKK AS

Who owns NARVIK FYSIOTERAPI OG FOTKLINIKK AS?

NINA HAUG VANEM is the largest registered owner, with 33.5%.

What is the revenue of NARVIK FYSIOTERAPI OG FOTKLINIKK AS?

NARVIK FYSIOTERAPI OG FOTKLINIKK AS had revenue of NOK 739,000 in 2025.

Where is NARVIK FYSIOTERAPI OG FOTKLINIKK AS based?

NARVIK FYSIOTERAPI OG FOTKLINIKK AS has its business address in Narvik.

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.