BIZTRAC BETA
General medical practice activities

LEGE THEA STEINERT AS

Org. no. 936893775 Limited company (AS) Nesodden Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −750
Equity NOK 20,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−750 kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-11-28.

LEGE THEA STEINERT AS is registered as a limited company in Nesodden, Akershus with organisation number 936893775. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Praksis som allmennlege og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp/drift av fast eiendom.”.

Key figures · 2025

Operating profit
NOK −750
Equity
NOK 20,000
Est. value
NOK 31,000

Financial health · 2025

Liquidity
2.93
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
65.8%
Weak
Equity as a share of total capital

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

Who owns LEGE THEA STEINERT AS?

THEA STEINERT
LEGE THEA STEINERT AS
· NOK −750 profit

LEGE THEA STEINERT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEGE THEA STEINERT AS

Who owns LEGE THEA STEINERT AS?

THEA STEINERT is the largest registered owner, with 100.0%.

Who is the general manager of LEGE THEA STEINERT AS?

Thea Steinert is registered as general manager of LEGE THEA STEINERT AS.

Where is LEGE THEA STEINERT AS based?

LEGE THEA STEINERT AS has its business address in Bjørnemyr.

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.