biztrac. BETA
COMPANY REGISTER PROFILE
933196275 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Retail sale of cosmetic and toilet articles

LISBETH BERGES URTESALVE AS

Org. no. 933196275 Limited company (AS) Melhus Incorporated 2024 Active
Operating profit NOK −311,000
Equity NOK −416,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

LISBETH BERGES URTESALVE AS is registered as a limited company in Melhus, Trøndelag with organisation number 933196275. The business is classified under retail sale of cosmetic and toilet articles (NACE 47.750). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utvikling, produksjon og salg av naturbaserte helseprodukter og annet som naturlig faller sammen med dette.”.

Former names: NATURENS KRAFT AS

Key figures · 2025

Operating profit
NOK −311,000
▼ −140 %
Equity
NOK −416,000
▼ −296 %

Financial health · 2025

Liquidity
0.11
Not satisfactory
Current assets ÷ current liabilities
Profitability
-355.9%
Not satisfactory
Return on total assets
Solidity
-818.4%
Weak
Equity as a share of total capital

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

Who owns LISBETH BERGES URTESALVE AS?

LISBETH BERGES URTESALVE AS
· NOK −311,000 profit

LISBETH BERGES URTESALVE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LISBETH BERGES URTESALVE AS

Who owns LISBETH BERGES URTESALVE AS?

Lisbeth Johanne Berge is the largest registered owner, with 50.0%.

Who is the general manager of LISBETH BERGES URTESALVE AS?

Edgar Wisløff is registered as general manager of LISBETH BERGES URTESALVE AS.

Where is LISBETH BERGES URTESALVE AS based?

LISBETH BERGES URTESALVE AS has its business address in Melhus.

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.