BIZTRAC BETA
Machining of metals

ALFSEN MEK. VERKSTED AS

Org. no. 911545977 Limited company (AS) Lillestrøm Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 162,000
Equity NOK −204,000
Incorporated 2013
Share capital NOK 30,000

Signals

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

ALFSEN MEK. VERKSTED AS is registered as a limited company in Lillestrøm, Akershus with organisation number 911545977. The business is classified under machining of metals (NACE 25.530). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Sveising og bearbeiding av metaller, oppføring drift og utleie av fast eiendom, herunder deltakelse i andre selskaper. Kjøp av fast eiendom og øvrige investeringer.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 162,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK 162,000
Equity
NOK −204,000
Est. value
NOK 898,000

Financial health · 2025

Liquidity
2.51
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-29.7%
Weak
Equity as a share of total capital

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

Who owns ALFSEN MEK. VERKSTED AS?

TOR SIGURD ALFSEN
ALFSEN MEK. VERKSTED AS
NOK 2.6m rev. · NOK 162,000 profit

ALFSEN MEK. VERKSTED AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ALFSEN MEK. VERKSTED AS

Who owns ALFSEN MEK. VERKSTED AS?

TOR SIGURD ALFSEN is the largest registered owner, with 100.0%.

What is the revenue of ALFSEN MEK. VERKSTED AS?

ALFSEN MEK. VERKSTED AS had revenue of NOK 2.6m in 2025.

Where is ALFSEN MEK. VERKSTED AS based?

ALFSEN MEK. VERKSTED AS has its business address in Lillestrøm.

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.