BIZTRAC BETA
Activities of orthopedists and chiropodists

VIBEKES FOTTERAPI AS

Org. no. 913703677 Limited company (AS) Bodø Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK 5,000
Equity NOK −41,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−41k kr).

VIBEKES FOTTERAPI AS is registered as a limited company in Bodø, Nordland with organisation number 913703677. The business is classified under activities of orthopedists and chiropodists (NACE 86.991). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Fotterapi med nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK 5,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK 5,000
Equity
NOK −41,000
Est. value
NOK 25,000

Financial health · 2024

Liquidity
0.85
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-18.8%
Weak
Equity as a share of total capital

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

Who owns VIBEKES FOTTERAPI AS?

VIBEKE ANGELSEN JOHANSEN
VIBEKES FOTTERAPI AS
NOK 1.2m rev. · NOK 5,000 profit

VIBEKES FOTTERAPI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VIBEKES FOTTERAPI AS

Who owns VIBEKES FOTTERAPI AS?

VIBEKE ANGELSEN JOHANSEN is the largest registered owner, with 100.0%.

What is the revenue of VIBEKES FOTTERAPI AS?

VIBEKES FOTTERAPI AS had revenue of NOK 1.2m in 2024.

Who is the general manager of VIBEKES FOTTERAPI AS?

Vibeke Angelsen Johansen is registered as general manager of VIBEKES FOTTERAPI AS.

Where is VIBEKES FOTTERAPI AS based?

VIBEKES FOTTERAPI AS has its business address in Bodø.

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.