biztrac. BETA
COMPANY REGISTER PROFILE
979206992 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
General medical practice activities

SLETTEBAKKEN LEGESENTER DA

Org. no. 979206992 General partnership with shared liability (DA) Bergen Incorporated 1997 Active
Revenue 2025 NOK 4.1m
Operating profit NOK −25,000
Equity NOK −53,000
Incorporated 1997

Signals

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

SLETTEBAKKEN LEGESENTER DA is registered as a general partnership with shared liability in Bergen, Vestland with organisation number 979206992. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 1997. The company's stated purpose is: “Alminnelig legepraksis.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.1m in revenue and NOK −25,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.1m
▲ +1 %
Operating profit
NOK −25,000
▲ +82 %
Equity
NOK −53,000
▲ +53 %

Financial health · 2025

Liquidity
0.76
Weak
Current assets ÷ current liabilities
Profitability
-9.0%
Not satisfactory
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 SLETTEBAKKEN LEGESENTER DA?

No shareholders are registered for SLETTEBAKKEN LEGESENTER DA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about SLETTEBAKKEN LEGESENTER DA

What is the revenue of SLETTEBAKKEN LEGESENTER DA?

SLETTEBAKKEN LEGESENTER DA had revenue of NOK 4.1m in 2025.

Who is the general manager of SLETTEBAKKEN LEGESENTER DA?

Mads Grimsland Wangsholm is registered as general manager of SLETTEBAKKEN LEGESENTER DA.

Where is SLETTEBAKKEN LEGESENTER DA based?

SLETTEBAKKEN LEGESENTER DA has its business address in Bergen.

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.