BIZTRAC BETA
Activities of orthopedists and chiropodists

WENCHES FOTTERAPI AS

Org. no. 934009843 Limited company (AS) Haugesund Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 833,000
Operating profit NOK 61,000
Equity NOK 38,000
Incorporated 2024
Share capital NOK 30,000

WENCHES FOTTERAPI AS is registered as a limited company in Haugesund, Rogaland with organisation number 934009843. The business is classified under activities of orthopedists and chiropodists (NACE 86.991). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Virksomheten skal drive med fotterapi, varesalg og veiledning/undervisning innen helse og velvære.”. The most recent filed accounts, for the 2025 financial year, show NOK 833,000 in revenue and NOK 61,000 in operating profit.

Key figures · 2025

Revenue
NOK 833,000
Operating profit
NOK 61,000
Equity
NOK 38,000
Est. value
NOK 303,000

Financial health · 2025

Liquidity
1.26
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.4%
Weak
Equity as a share of total capital

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

Who owns WENCHES FOTTERAPI AS?

WENCHE KARLSEN
WENCHES FOTTERAPI AS
NOK 833,000 rev. · NOK 61,000 profit

WENCHES FOTTERAPI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WENCHES FOTTERAPI AS

Who owns WENCHES FOTTERAPI AS?

WENCHE KARLSEN is the largest registered owner, with 100.0%.

What is the revenue of WENCHES FOTTERAPI AS?

WENCHES FOTTERAPI AS had revenue of NOK 833,000 in 2025.

Who is the general manager of WENCHES FOTTERAPI AS?

Wenche Karlsen is registered as general manager of WENCHES FOTTERAPI AS.

Where is WENCHES FOTTERAPI AS based?

WENCHES FOTTERAPI AS has its business address in Haugesund.

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.