BIZTRAC BETA
Manufacture of other plastic products

NFM TECHNOLOGY AS

Org. no. 987444282 Limited company (AS) Nordre Follo Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 98.7m
Operating profit NOK 12.0m
Equity NOK 29.6m
Incorporated 2004
Employees 19
Share capital NOK 125,000

NFM TECHNOLOGY AS is registered as a limited company in Nordre Follo, Akershus with organisation number 987444282. The business is classified under manufacture of other plastic products (NACE 22.260). The company was incorporated in 2004 and has 19 registered employees. Registered share capital is NOK 125,000, divided into 1250 shares. The company's stated purpose is: “Produksjon og salg av komposittprodukter basert på miljøvennlige, fiberarmerte termoplastmaterialer, samt å delta i andre innenlansake og utenlandske foretagender innenfor samme virksomhetsområder.”. The most recent filed accounts, for the 2024 financial year, show NOK 98.7m in revenue and NOK 12.0m in operating profit.

Key figures · 2024

Revenue
NOK 98.7m
Operating profit
NOK 12.0m
Equity
NOK 29.6m
Est. value
NOK 58.6m

Financial health · 2024

Liquidity
1.21
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
30.0%
Good
Equity as a share of total capital

Who owns NFM TECHNOLOGY AS?

NFM AS
NFM TECHNOLOGY AS
NOK 98.7m rev. · NOK 12.0m profit

NFM TECHNOLOGY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NFM TECHNOLOGY AS

Who owns NFM TECHNOLOGY AS?

NFM AS is the largest registered owner, with 100.0%.

What is the revenue of NFM TECHNOLOGY AS?

NFM TECHNOLOGY AS had revenue of NOK 98.7m in 2024.

Who is the general manager of NFM TECHNOLOGY AS?

Tor Inge Thun is registered as general manager of NFM TECHNOLOGY AS.

Where is NFM TECHNOLOGY AS based?

NFM TECHNOLOGY AS has its business address in Ski.

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.