BIZTRAC BETA
Other technical consultancy

PLUG LOFOTEN AS

Org. no. 929681347 Limited company (AS) Vågan Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 68,000
Operating profit NOK −1.8m
Equity NOK 4.8m
Incorporated 2022
Share capital NOK 1.5m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,8 mill kr).

PLUG LOFOTEN AS is registered as a limited company in Vågan, Nordland with organisation number 929681347. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2022. Registered share capital is NOK 1.5m, divided into 1000 shares. The company's stated purpose is: “Å utvikle, eie og drifte infrastruktur for landstrøm og lading med utgangspunkt i maritimt behov for nullutslippsløsninger for kystnære fartøygrupper, samt virksomhet knyttet til dette. Selskapet skal drives etter forretningsmessige prinsipper og har som mål å skape overskudd for eierne.”. The most recent filed accounts, for the 2024 financial year, show NOK 68,000 in revenue and NOK −1.8m in operating profit.

Key figures · 2024

Revenue
NOK 68,000
Operating profit
NOK −1.8m
Equity
NOK 4.8m
Est. value
NOK 2.4m

Financial health · 2024

Liquidity
1.77
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
69.0%
Very good
Equity as a share of total capital

Who owns PLUG LOFOTEN AS?

LOFOTKRAFT MULIGHETER AS
PLUG LOFOTEN AS
NOK 68,000 rev. · NOK −1.8m profit

PLUG LOFOTEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about PLUG LOFOTEN AS

Who owns PLUG LOFOTEN AS?

LOFOTKRAFT MULIGHETER AS is the largest registered owner, with 50.0%.

What is the revenue of PLUG LOFOTEN AS?

PLUG LOFOTEN AS had revenue of NOK 68,000 in 2024.

Where is PLUG LOFOTEN AS based?

PLUG LOFOTEN AS has its business address in Svolvær.

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.