BIZTRAC BETA
Repair and maintenance of motor vehicles

LERSBRYGGEN BIL AS

Org. no. 986828850 Limited company (AS) Holmestrand Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 8.5m
Operating profit NOK 231,000
Equity NOK 266,000
Incorporated 2004
Employees 7
Share capital NOK 100,000

LERSBRYGGEN BIL AS is registered as a limited company in Holmestrand, Vestfold with organisation number 986828850. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2004 and has 7 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Bilverksted, kjøp og salg av biler og alt som hører naturlig med i den forbindelse. Selskapet skal også ha anledning til å eie aksjer i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.5m in revenue and NOK 231,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.5m
Operating profit
NOK 231,000
Equity
NOK 266,000
Est. value
NOK 862,000

Financial health · 2024

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

Who owns LERSBRYGGEN BIL AS?

LUKASZ KORPALSKI
LERSBRYGGEN BIL AS
NOK 8.5m rev. · NOK 231,000 profit

LERSBRYGGEN BIL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LERSBRYGGEN BIL AS

Who owns LERSBRYGGEN BIL AS?

LUKASZ KORPALSKI is the largest registered owner, with 100.0%.

What is the revenue of LERSBRYGGEN BIL AS?

LERSBRYGGEN BIL AS had revenue of NOK 8.5m in 2024.

Who is the general manager of LERSBRYGGEN BIL AS?

Lukasz Korpalski is registered as general manager of LERSBRYGGEN BIL AS.

Where is LERSBRYGGEN BIL AS based?

LERSBRYGGEN BIL AS has its business address in Sande I Vestfold.

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.