biztrac. BETA
COMPANY REGISTER PROFILE
917039186 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other cleaning activities

FØ LMT AS

Org. no. 917039186 Limited company (AS) Skiptvet Incorporated 2017 Active
Revenue 2025 NOK 1.9m
Operating profit NOK −591,000
Equity NOK −915,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

FØ LMT AS is registered as a limited company in Skiptvet, Østfold with organisation number 917039186. The business is classified under other cleaning activities (NACE 81.230). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utleie av maskiner og arbeidskraft. Snøbrøyting, strøing, graving, transport og anleggsgartnerarbeid.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK −591,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
▼ −19 %
Operating profit
NOK −591,000
▼ −1282 %
Equity
NOK −915,000
▼ −212 %

Financial health · 2025

Liquidity
2.31
Very good
Current assets ÷ current liabilities
Profitability
-70.0%
Not satisfactory
Return on total assets
Solidity
-189.5%
Weak
Equity as a share of total capital

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

Who owns FØ LMT AS?

FØ LMT AS
NOK 1.9m rev. · NOK −591,000 profit

FØ LMT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FØ LMT AS

Who owns FØ LMT AS?

Fred Øivind Øiestad is the largest registered owner, with 100.0%.

What is the revenue of FØ LMT AS?

FØ LMT AS had revenue of NOK 1.9m in 2025.

Who is the general manager of FØ LMT AS?

Fred Øivind Øiestad is registered as general manager of FØ LMT AS.

Where is FØ LMT AS based?

FØ LMT AS has its business address in Skiptvet.

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

Report a problem

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