BIZTRAC BETA
Civil engineering activities

LOFOTEN TEKNISKE AS

Org. no. 930105007 Limited company (AS) Vestvågøy Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 8.9m
Operating profit NOK 2.1m
Equity NOK 3.1m
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-05-04 Adresseendring registrert 2026-05-04.

LOFOTEN TEKNISKE AS is registered as a limited company in Vestvågøy, Nordland with organisation number 930105007. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Rådgivende ingeniørvirksomhet eller virksomhet som står i forbindelse med dette, prosjektledelse og prosjektutvikling.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.9m in revenue and NOK 2.1m in operating profit.

Key figures · 2025

Revenue
NOK 8.9m
Operating profit
NOK 2.1m
Equity
NOK 3.1m
Est. value
NOK 10.0m

Financial health · 2025

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

Who owns LOFOTEN TEKNISKE AS?

NIILO FRANS-EMIL PAIVIO NISSINEN
LOFOTEN TEKNISKE AS
NOK 8.9m rev. · NOK 2.1m profit

LOFOTEN TEKNISKE AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LOFOTEN TEKNISKE AS

Who owns LOFOTEN TEKNISKE AS?

NIILO FRANS-EMIL PAIVIO NISSINEN is the largest registered owner, with 51.0%.

What is the revenue of LOFOTEN TEKNISKE AS?

LOFOTEN TEKNISKE AS had revenue of NOK 8.9m in 2025.

Who is the general manager of LOFOTEN TEKNISKE AS?

Stian Sannes Pedersen is registered as general manager of LOFOTEN TEKNISKE AS.

Where is LOFOTEN TEKNISKE AS based?

LOFOTEN TEKNISKE 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.