biztrac. BETA
COMPANY REGISTER PROFILE
933325946 ORG. NO. 2025 ACCOUNTS 11 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

GARTNERITOMTA BOLIGUTVIKLING AS

Org. no. 933325946 Limited company (AS) Drammen Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 94.5m
Operating profit NOK 2.6m
Equity NOK 2.0m
Incorporated 2024
Share capital NOK 30,000

GARTNERITOMTA BOLIGUTVIKLING AS is registered as a limited company in Drammen, Buskerud with organisation number 933325946. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøpe, utvikle, utbygge og selge eiendom i Færder kommune.”. The most recent filed accounts, for the 2025 financial year, show NOK 94.5m in revenue and NOK 2.6m in operating profit.

Former names: ALFANOR 24017 AS

Key figures · 2025

Revenue
NOK 94.5m
Operating profit
NOK 2.6m
▲ +14169 %
Equity
NOK 2.0m
▲ +55359 %
Est. value
NOK 6.6m

Financial health · 2025

Liquidity
50.83
Very good
Current assets ÷ current liabilities
Profitability
2.7%
Weak
Return on total assets
Solidity
2.1%
Not satisfactory
Equity as a share of total capital

Who owns GARTNERITOMTA BOLIGUTVIKLING AS?

GARTNERITOMTA BOLIGUTVIKLING AS
NOK 94.5m rev. · NOK 2.6m profit

GARTNERITOMTA BOLIGUTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GARTNERITOMTA BOLIGUTVIKLING AS

Who owns GARTNERITOMTA BOLIGUTVIKLING AS?

JENSEN EIENDOMUTVIKLING AS is the largest registered owner, with 50.0%.

What is the revenue of GARTNERITOMTA BOLIGUTVIKLING AS?

GARTNERITOMTA BOLIGUTVIKLING AS had revenue of NOK 94.5m in 2025.

Where is GARTNERITOMTA BOLIGUTVIKLING AS based?

GARTNERITOMTA BOLIGUTVIKLING AS has its business address in Drammen.

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.