BIZTRAC BETA
Repair and maintenance of motor vehicles

GRENLAND ANTIRUST AS

Org. no. 915921884 Limited company (AS) Skien Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 2.9m
Operating profit NOK 587,000
Equity NOK 554,000
Incorporated 2015
Share capital NOK 30,000

GRENLAND ANTIRUST AS is registered as a limited company in Skien, Telemark with organisation number 915921884. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Vedlikehold, herunder rustbehandling av motorkjøretøyer, samt kjøp og salg av motorkjøretøyer og investering i andre selskaper, og virksomhet som herved hører sammen med denne virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.9m in revenue and NOK 587,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.9m
Operating profit
NOK 587,000
Equity
NOK 554,000
Est. value
NOK 2.2m

Financial health · 2025

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

Who owns GRENLAND ANTIRUST AS?

RAL EIENDOM AS
GRENLAND ANTIRUST AS
NOK 2.9m rev. · NOK 587,000 profit

GRENLAND ANTIRUST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GRENLAND ANTIRUST AS

Who owns GRENLAND ANTIRUST AS?

RAL EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of GRENLAND ANTIRUST AS?

GRENLAND ANTIRUST AS had revenue of NOK 2.9m in 2025.

Who is the general manager of GRENLAND ANTIRUST AS?

Rune Anders Langeland is registered as general manager of GRENLAND ANTIRUST AS.

Where is GRENLAND ANTIRUST AS based?

GRENLAND ANTIRUST 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.