BIZTRAC BETA
Other health services

SMERTENS KILDE AS

Org. no. 918747125 Limited company (AS) Sola Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK −403,000
Equity NOK −68,000
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−68k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−403k kr).

SMERTENS KILDE AS is registered as a limited company in Sola, Rogaland with organisation number 918747125. The business is classified under other health services (NACE 86.993). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Alternativ behandling refleksologi.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK −403,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK −403,000
Equity
NOK −68,000

Financial health · 2025

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

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

Who owns SMERTENS KILDE AS?

Ingfrid Margrethe Vigdel
SMERTENS KILDE AS
NOK 1.5m rev. · NOK −403,000 profit

SMERTENS KILDE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SMERTENS KILDE AS

Who owns SMERTENS KILDE AS?

Ingfrid Margrethe Vigdel is the largest registered owner, with 100.0%.

What is the revenue of SMERTENS KILDE AS?

SMERTENS KILDE AS had revenue of NOK 1.5m in 2025.

Who is the general manager of SMERTENS KILDE AS?

Ingfrid Margrethe Vigdel is registered as general manager of SMERTENS KILDE AS.

Where is SMERTENS KILDE AS based?

SMERTENS KILDE AS has its business address in Røyneberg.

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.