BIZTRAC BETA
Rental and leasing of other machinery, equipment and tangible goods n.e.c.

AILT (E) MULIG AS

Org. no. 822083102 Limited company (AS) Steinkjer Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 208,000
Equity NOK 932,000
Incorporated 2018
Share capital NOK 30,000

AILT (E) MULIG AS is registered as a limited company in Steinkjer, Trøndelag with organisation number 822083102. The business is classified under rental and leasing of other machinery, equipment and tangible goods n.e.c. (NACE 77.390). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utleie av sag, salg av materiell, utleie av brakkebolig, maskinentreprenørvirksomhet samt annet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 208,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 208,000
Equity
NOK 932,000
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns AILT (E) MULIG AS?

SISSEL FELLINGFORS
AILT (E) MULIG AS
NOK 1.1m rev. · NOK 208,000 profit

AILT (E) MULIG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about AILT (E) MULIG AS

Who owns AILT (E) MULIG AS?

SISSEL FELLINGFORS is the largest registered owner, with 50.0%.

What is the revenue of AILT (E) MULIG AS?

AILT (E) MULIG AS had revenue of NOK 1.1m in 2025.

Who is the general manager of AILT (E) MULIG AS?

Bjørn Edvin Sæther is registered as general manager of AILT (E) MULIG AS.

Where is AILT (E) MULIG AS based?

AILT (E) MULIG AS has its business address in Beitstad.

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.