BIZTRAC BETA
COMPANY REGISTER PROFILE
926171038 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

LFT AS

Org. no. 926171038 Limited company (AS) Ørsta Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −24,000
Equity NOK 6.5m
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−24k kr).

LFT AS is registered as a limited company in Ørsta, Møre og Romsdal with organisation number 926171038. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eie aksjer i andre selskaper, investere i børsnoterte selskaper og fast eiendom.”.

Key figures · 2025

Operating profit
NOK −24,000
▼ −90 %
Equity
NOK 6.5m
▲ +39 %
Est. value
NOK 18.0m

Financial health · 2025

Liquidity
88.06
Very good
Current assets ÷ current liabilities
Profitability
40.2%
Very good
Return on total assets
Solidity
99.0%
Very good
Equity as a share of total capital

Who owns LFT AS?

LFT AS
· NOK −24,000 profit

LFT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LFT AS own?

LFT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LFT AS

Who owns LFT AS?

TORD FURSETH LIADAL is the largest registered owner, with 100.0%.

Where is LFT AS based?

LFT AS has its business address in Ørsta.

Property

Business address c/o Tord Furseth Liadal Liadalsvegen 886, 6152 Ørsta
Cadastral unit 1520-3/15/0/0
Building Enebolig · 2 units

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.