BIZTRAC BETA
Rental and operating of own or leased real estate

GILHUSVEIEN 10 AS

Org. no. 964625107 Limited company (AS) Drammen Incorporated 1992 Active
Ownership graph ↗
Revenue 2024 NOK 182.6m
Operating profit NOK 181.7m
Equity NOK 7.2m
Incorporated 1992
Share capital NOK 364,000

GILHUSVEIEN 10 AS is registered as a limited company in Drammen, Buskerud with organisation number 964625107. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1992. Registered share capital is NOK 364,000, divided into 910 shares. The company's stated purpose is: “Handelvirksomhet, utleie av maskiner og utstyr samt tilhørende virksomhet og forvaltning og utleie av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 182.6m in revenue and NOK 181.7m in operating profit.

Key figures · 2024

Revenue
NOK 182.6m
Operating profit
NOK 181.7m
Equity
NOK 7.2m
Est. value
NOK 352.7m

Financial health · 2024

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

Who owns GILHUSVEIEN 10 AS?

BVAR AS
GILHUSVEIEN 10 AS
NOK 182.6m rev. · NOK 181.7m profit

GILHUSVEIEN 10 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

GILHUSVEIEN 10 AS er morselskap for 18 datterselskaper:

Frequently asked questions about GILHUSVEIEN 10 AS

Who owns GILHUSVEIEN 10 AS?

BVAR AS is the largest registered owner, with 100.0%.

What is the revenue of GILHUSVEIEN 10 AS?

GILHUSVEIEN 10 AS had revenue of NOK 182.6m in 2024.

Who is the general manager of GILHUSVEIEN 10 AS?

Ida Christiane Mikkelsen is registered as general manager of GILHUSVEIEN 10 AS.

Where is GILHUSVEIEN 10 AS based?

GILHUSVEIEN 10 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 15.06.2026.

Report a problem

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