BIZTRAC BETA
General medical practice activities

STEKKE LEGESENTER AS

Org. no. 896901532 Limited company (AS) Verdal Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 5.3m
Operating profit NOK 320,000
Equity NOK 123,000
Incorporated 2011
Employees 12
Share capital NOK 102,000

STEKKE LEGESENTER AS is registered as a limited company in Verdal, Trøndelag with organisation number 896901532. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2011 and has 12 registered employees. Registered share capital is NOK 102,000, divided into 102 shares. The company's stated purpose is: “Legesenter, helsetjenester, informasjon og salg samt deltagelse i selskaper av samme eller annen art gjennom aksjetegning eller på annen måte.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.3m in revenue and NOK 320,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.3m
Operating profit
NOK 320,000
Equity
NOK 123,000
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns STEKKE LEGESENTER AS?

LENE MARIT NESS-JENSEN
STEKKE LEGESENTER AS
NOK 5.3m rev. · NOK 320,000 profit

STEKKE LEGESENTER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STEKKE LEGESENTER AS

Who owns STEKKE LEGESENTER AS?

LENE MARIT NESS-JENSEN is the largest registered owner, with 50.0%.

What is the revenue of STEKKE LEGESENTER AS?

STEKKE LEGESENTER AS had revenue of NOK 5.3m in 2025.

Who is the general manager of STEKKE LEGESENTER AS?

Guri Holmvik is registered as general manager of STEKKE LEGESENTER AS.

Where is STEKKE LEGESENTER AS based?

STEKKE LEGESENTER AS has its business address in Verdal.

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.