BIZTRAC BETA
Rental and operating of own or leased real estate

APOTEKERGAARDEN 1775 AS

Org. no. 923567496 Limited company (AS) Bamble Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 626,000
Equity NOK 2.9m
Incorporated 2019
Share capital NOK 30,000

APOTEKERGAARDEN 1775 AS is registered as a limited company in Bamble, Telemark with organisation number 923567496. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eie, drift og utleie av fast eiendom, eie aksjer i andre selskap, samt virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 626,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 626,000
Equity
NOK 2.9m
Est. value
NOK 3.6m

Financial health · 2024

Liquidity
1.11
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
50.2%
Very good
Equity as a share of total capital

Who owns APOTEKERGAARDEN 1775 AS?

SBO HOLDING AS
APOTEKERGAARDEN 1775 AS
NOK 1.5m rev. · NOK 626,000 profit

APOTEKERGAARDEN 1775 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about APOTEKERGAARDEN 1775 AS

Who owns APOTEKERGAARDEN 1775 AS?

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

What is the revenue of APOTEKERGAARDEN 1775 AS?

APOTEKERGAARDEN 1775 AS had revenue of NOK 1.5m in 2024.

Who is the general manager of APOTEKERGAARDEN 1775 AS?

Hege Opedal is registered as general manager of APOTEKERGAARDEN 1775 AS.

Where is APOTEKERGAARDEN 1775 AS based?

APOTEKERGAARDEN 1775 AS has its business address in Langesund.

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.