BIZTRAC BETA
COMPANY REGISTER PROFILE
914163986 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Repair and maintenance of motor vehicles

LOFOTEN BILVERKSTED AS

Org. no. 914163986 Limited company (AS) Vestvågøy Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK −582,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−582k kr).

LOFOTEN BILVERKSTED AS is registered as a limited company in Vestvågøy, Nordland with organisation number 914163986. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Drive med rustsveising, karosseriarbeider, lakkforberedelser, lakkering, motorreparasjoner etc.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK −582,000

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
Not available
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LOFOTEN BILVERKSTED AS?

ANDRIS BALTRUNKIS
LOFOTEN BILVERKSTED AS
NOK 0 rev. · NOK 0 profit

LOFOTEN BILVERKSTED AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LOFOTEN BILVERKSTED AS

Who owns LOFOTEN BILVERKSTED AS?

ANDRIS BALTRUNKIS is the largest registered owner, with 100.0%.

What is the revenue of LOFOTEN BILVERKSTED AS?

LOFOTEN BILVERKSTED AS had revenue of NOK 0 in 2025.

Where is LOFOTEN BILVERKSTED AS based?

LOFOTEN BILVERKSTED AS has its business address in Leknes.

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.