BIZTRAC BETA
Repair and maintenance of motor vehicles

GULSKOGEN AUTOLAKK AS

Org. no. 993359653 Limited company (AS) Drammen Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 7.2m
Operating profit NOK 257,000
Equity NOK 1.1m
Incorporated 2008
Share capital NOK 100,000

GULSKOGEN AUTOLAKK AS is registered as a limited company in Drammen, Buskerud with organisation number 993359653. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å drive verksted lakkering av kjøretøy, reklamevirksomhet samt utleie av fast eiendom, og ellers alt hva herved naturlig står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.2m in revenue and NOK 257,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.2m
Operating profit
NOK 257,000
Equity
NOK 1.1m
Est. value
NOK 1.5m

Financial health · 2025

Liquidity
1.27
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.4%
Good
Equity as a share of total capital

Who owns GULSKOGEN AUTOLAKK AS?

JOSTEIN FOLKEDAL
GULSKOGEN AUTOLAKK AS
NOK 7.2m rev. · NOK 257,000 profit

GULSKOGEN AUTOLAKK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GULSKOGEN AUTOLAKK AS

Who owns GULSKOGEN AUTOLAKK AS?

JOSTEIN FOLKEDAL is the largest registered owner, with 50.0%.

What is the revenue of GULSKOGEN AUTOLAKK AS?

GULSKOGEN AUTOLAKK AS had revenue of NOK 7.2m in 2024.

Who is the general manager of GULSKOGEN AUTOLAKK AS?

Øyvind Nilsen is registered as general manager of GULSKOGEN AUTOLAKK AS.

Where is GULSKOGEN AUTOLAKK AS based?

GULSKOGEN AUTOLAKK AS has its business address in Solbergelva.

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.