BIZTRAC BETA
Repair and maintenance of motor vehicles

LAKK-SERVICE AS

Org. no. 936319297 Limited company (AS) Tysvær Incorporated 1985 Active
Ownership graph ↗
Revenue 2024 NOK 8.7m
Operating profit NOK 854,000
Equity NOK 352,000
Incorporated 1985
Employees 7
Share capital NOK 330,000

Signals

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

LAKK-SERVICE AS is registered as a limited company in Tysvær, Rogaland with organisation number 936319297. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 1985 and has 7 registered employees. Registered share capital is NOK 330,000, divided into 550 shares. The company's stated purpose is: “Billakkering og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.7m in revenue and NOK 854,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.7m
Operating profit
NOK 854,000
Equity
NOK 352,000
Est. value
NOK 3.4m

Financial health · 2024

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

Who owns LAKK-SERVICE AS?

NERNES EIENDOM AS
LAKK-SERVICE AS
NOK 8.7m rev. · NOK 854,000 profit

LAKK-SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LAKK-SERVICE AS

Who owns LAKK-SERVICE AS?

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

What is the revenue of LAKK-SERVICE AS?

LAKK-SERVICE AS had revenue of NOK 8.7m in 2024.

Who is the general manager of LAKK-SERVICE AS?

Bjørn Martin Nernes is registered as general manager of LAKK-SERVICE AS.

Where is LAKK-SERVICE AS based?

LAKK-SERVICE AS has its business address in Førresfjorden.

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.