biztrac. BETA
COMPANY REGISTER PROFILE
928993833 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other health services

GABELS PARK AS

Org. no. 928993833 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 28.9m
Operating profit NOK 712,000
Equity NOK 4.2m
Incorporated 2022
Employees 17
Share capital NOK 50,000

GABELS PARK AS is registered as a limited company in Oslo, Oslo with organisation number 928993833. The business is classified under other health services (NACE 86.993). The company was incorporated in 2022 and has 17 registered employees. Registered share capital is NOK 50,000, divided into 100 shares. The company's stated purpose is: “Sykepleie, helse- og praktisk hjelp, assistanse, aktiviteter, servering ved utleie av tilpassede boenheter til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 28.9m in revenue and NOK 712,000 in operating profit.

Former names: ALFANOR 22020 AS, 2CARE BPA AS

Key figures · 2025

Revenue
NOK 28.9m
▲ +21 %
Operating profit
NOK 712,000
▲ +293 %
Equity
NOK 4.2m
▲ +15 %
Est. value
NOK 5.2m

Financial health · 2025

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

Who owns GABELS PARK AS?

GABELS PARK AS
NOK 28.9m rev. · NOK 712,000 profit

GABELS PARK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GABELS PARK AS

Who owns GABELS PARK AS?

2CARE AS is the largest registered owner, with 100.0%.

What is the revenue of GABELS PARK AS?

GABELS PARK AS had revenue of NOK 28.9m in 2025.

Who is the general manager of GABELS PARK AS?

Henriette Marie Hansson Nilssen is registered as general manager of GABELS PARK AS.

Where is GABELS PARK AS based?

GABELS PARK 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.