BIZTRAC BETA
Repair and maintenance of motor vehicles

GYLDENLØVE BILSERVICE AS

Org. no. 978633919 Limited company (AS) Drammen Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 16.0m
Operating profit NOK 1.5m
Equity NOK 3.3m
Incorporated 1997
Employees 13
Share capital NOK 300,000

GYLDENLØVE BILSERVICE AS is registered as a limited company in Drammen, Buskerud with organisation number 978633919. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 1997 and has 13 registered employees. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Drive bilservice og alt som står i forbindelse med dette, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.0m in revenue and NOK 1.5m in operating profit.

Key figures · 2024

Revenue
NOK 16.0m
Operating profit
NOK 1.5m
Equity
NOK 3.3m
Est. value
NOK 7.0m

Financial health · 2024

Liquidity
1.52
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
41.8%
Very good
Equity as a share of total capital

Who owns GYLDENLØVE BILSERVICE AS?

SVEN FOLKE EDVARD NELSON
GYLDENLØVE BILSERVICE AS
NOK 16.0m rev. · NOK 1.5m profit

GYLDENLØVE BILSERVICE AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about GYLDENLØVE BILSERVICE AS

Who owns GYLDENLØVE BILSERVICE AS?

SVEN FOLKE EDVARD NELSON is the largest registered owner, with 23.3%.

What is the revenue of GYLDENLØVE BILSERVICE AS?

GYLDENLØVE BILSERVICE AS had revenue of NOK 16.0m in 2024.

Who is the general manager of GYLDENLØVE BILSERVICE AS?

Henrik Gautneb is registered as general manager of GYLDENLØVE BILSERVICE AS.

Where is GYLDENLØVE BILSERVICE AS based?

GYLDENLØVE BILSERVICE 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.