BIZTRAC BETA
Retail sale of motor vehicles

GRENLAND BILSERVICE AS

Org. no. 919134062 Limited company (AS) Skien Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 152.0m
Operating profit NOK 691,000
Equity NOK 10.0m
Incorporated 2017
Employees 22
Share capital NOK 10.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GRENLAND BILSERVICE AS is registered as a limited company in Skien, Telemark with organisation number 919134062. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2017 and has 22 registered employees. Registered share capital is NOK 10.0m, divided into 33217 shares. The company's stated purpose is: “Kjøp, salg, reparasjon og service av biler og alt som har sammenheng med dette, samt deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 152.0m in revenue and NOK 691,000 in operating profit.

Key figures · 2024

Revenue
NOK 152.0m
Operating profit
NOK 691,000
Equity
NOK 10.0m
Est. value
NOK 7.4m

Financial health · 2024

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

Who owns GRENLAND BILSERVICE AS?

GUMPENS AUTO AS
GRENLAND BILSERVICE AS
NOK 152.0m rev. · NOK 691,000 profit

GRENLAND BILSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GRENLAND BILSERVICE AS

Who owns GRENLAND BILSERVICE AS?

GUMPENS AUTO AS is the largest registered owner, with 100.0%.

What is the revenue of GRENLAND BILSERVICE AS?

GRENLAND BILSERVICE AS had revenue of NOK 152.0m in 2024.

Where is GRENLAND BILSERVICE AS based?

GRENLAND BILSERVICE AS has its business address in Skien.

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.