BIZTRAC BETA
Manufacture of other fabricated metal products n.e.c.

PLATETEKNIKK AS

Org. no. 985677131 Limited company (AS) Indre Østfold Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 8.9m
Operating profit NOK 360,000
Equity NOK 2.5m
Incorporated 2003
Employees 6
Share capital NOK 100,000

PLATETEKNIKK AS is registered as a limited company in Indre Østfold, Østfold with organisation number 985677131. The business is classified under manufacture of other fabricated metal products n.e.c. (NACE 25.990). The company was incorporated in 2003 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Produksjon og handel og alt hva herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.9m in revenue and NOK 360,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.9m
Operating profit
NOK 360,000
Equity
NOK 2.5m
Est. value
NOK 2.1m

Financial health · 2025

Liquidity
0.93
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.7%
Satisfactory
Equity as a share of total capital

Who owns PLATETEKNIKK AS?

GEIR ØSTLI
PLATETEKNIKK AS
NOK 8.9m rev. · NOK 360,000 profit

PLATETEKNIKK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PLATETEKNIKK AS own?

PLATETEKNIKK AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about PLATETEKNIKK AS

Who owns PLATETEKNIKK AS?

GEIR ØSTLI is the largest registered owner, with 100.0%.

What is the revenue of PLATETEKNIKK AS?

PLATETEKNIKK AS had revenue of NOK 8.9m in 2025.

Who is the general manager of PLATETEKNIKK AS?

Geir Østli is registered as general manager of PLATETEKNIKK AS.

Where is PLATETEKNIKK AS based?

PLATETEKNIKK AS has its business address in Spydeberg.

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.