BIZTRAC BETA
General medical practice activities

DRØBAK LEGESENTER AS

Org. no. 913065999 Limited company (AS) Frogn Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK −7
Equity NOK 30,000
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7 kr).

DRØBAK LEGESENTER AS is registered as a limited company in Frogn, Akershus with organisation number 913065999. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Allmennpraktiserende legetjenester”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK −7 in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
Operating profit
NOK −7
Equity
NOK 30,000
Est. value
NOK 2.2m

Financial health · 2025

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

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

Who owns DRØBAK LEGESENTER AS?

NEELESH SATEESH KASBEKAR
DRØBAK LEGESENTER AS
NOK 2.7m rev. · NOK −7 profit

DRØBAK LEGESENTER AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about DRØBAK LEGESENTER AS

Who owns DRØBAK LEGESENTER AS?

NEELESH SATEESH KASBEKAR is the largest registered owner, with 34.0%.

What is the revenue of DRØBAK LEGESENTER AS?

DRØBAK LEGESENTER AS had revenue of NOK 2.7m in 2025.

Who is the general manager of DRØBAK LEGESENTER AS?

Neelesh Sateesh Kasbekar is registered as general manager of DRØBAK LEGESENTER AS.

Where is DRØBAK LEGESENTER AS based?

DRØBAK LEGESENTER AS has its business address in Drøbak.

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.