BIZTRAC BETA
Repair and maintenance of motor vehicles

BRYNE BIL AS

Org. no. 996783197 Limited company (AS) Time Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 38.9m
Operating profit NOK 2.2m
Equity NOK 2.7m
Incorporated 2011
Employees 26
Share capital NOK 100,000

BRYNE BIL AS is registered as a limited company in Time, Rogaland with organisation number 996783197. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2011 and has 26 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive autorisert bilverksted samt bilskade, bilsalg og andre produkter/tjenester som hører til under dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 38.9m in revenue and NOK 2.2m in operating profit.

Key figures · 2024

Revenue
NOK 38.9m
Operating profit
NOK 2.2m
Equity
NOK 2.7m
Est. value
NOK 9.6m

Financial health · 2024

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

Who owns BRYNE BIL AS?

BRYNE BIL GROUP AS
BRYNE BIL AS
NOK 38.9m rev. · NOK 2.2m profit

BRYNE BIL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRYNE BIL AS

Who owns BRYNE BIL AS?

BRYNE BIL GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of BRYNE BIL AS?

BRYNE BIL AS had revenue of NOK 38.9m in 2024.

Who is the general manager of BRYNE BIL AS?

Morten Abelsnes is registered as general manager of BRYNE BIL AS.

Where is BRYNE BIL AS based?

BRYNE BIL AS has its business address in Bryne.

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.