BIZTRAC BETA
General medical practice activities

LINDEBERG LEGESENTER AS

Org. no. 911559463 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 5.7m
Operating profit NOK 421,000
Equity NOK 369,000
Incorporated 2012
Employees 5
Share capital NOK 30,000

LINDEBERG LEGESENTER AS is registered as a limited company in Oslo, Oslo with organisation number 911559463. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2012 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Å være et driftsselskap som skal tilrettelegge og drifte fellesfunksjonene for de legevirksomhetene som utføres i selskapet.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.7m in revenue and NOK 421,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.7m
Operating profit
NOK 421,000
Equity
NOK 369,000
Est. value
NOK 2.2m

Financial health · 2025

Liquidity
1.37
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
33.1%
Good
Equity as a share of total capital

Who owns LINDEBERG LEGESENTER AS?

SHIVENDRA NATH KAKAR
LINDEBERG LEGESENTER AS
NOK 5.7m rev. · NOK 421,000 profit

LINDEBERG LEGESENTER AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about LINDEBERG LEGESENTER AS

Who owns LINDEBERG LEGESENTER AS?

SHIVENDRA NATH KAKAR is the largest registered owner, with 20.0%.

What is the revenue of LINDEBERG LEGESENTER AS?

LINDEBERG LEGESENTER AS had revenue of NOK 5.7m in 2025.

Who is the general manager of LINDEBERG LEGESENTER AS?

Podimahatmaya Tharma is registered as general manager of LINDEBERG LEGESENTER AS.

Where is LINDEBERG LEGESENTER AS based?

LINDEBERG LEGESENTER AS has its business address in Oslo.

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.