BIZTRAC BETA
General medical practice activities

GRÜNERLØKKA LEGESENTER AS

Org. no. 926181823 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 3.5m
Operating profit NOK 77,000
Equity NOK 154,000
Incorporated 2020
Employees 7
Share capital NOK 30,000

GRÜNERLØKKA LEGESENTER AS is registered as a limited company in Oslo, Oslo with organisation number 926181823. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2020 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Legevirksomhet og det som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.5m in revenue and NOK 77,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.5m
Operating profit
NOK 77,000
Equity
NOK 154,000
Est. value
NOK 450,000

Financial health · 2024

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

Who owns GRÜNERLØKKA LEGESENTER AS?

HEXSPOOR HOLDING AS
GRÜNERLØKKA LEGESENTER AS
NOK 3.5m rev. · NOK 77,000 profit

GRÜNERLØKKA LEGESENTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GRÜNERLØKKA LEGESENTER AS

Who owns GRÜNERLØKKA LEGESENTER AS?

HEXSPOOR HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of GRÜNERLØKKA LEGESENTER AS?

GRÜNERLØKKA LEGESENTER AS had revenue of NOK 3.5m in 2024.

Who is the general manager of GRÜNERLØKKA LEGESENTER AS?

Minou Saga Hexspoor is registered as general manager of GRÜNERLØKKA LEGESENTER AS.

Where is GRÜNERLØKKA LEGESENTER AS based?

GRÜNERLØKKA 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.