BIZTRAC BETA
Manufacture of cordage, rope, twine and netting

TRAPNOR AS

Org. no. 824370842 Limited company (AS) Kåfjord Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 272,000
Operating profit NOK 183,000
Equity NOK 143,000
Incorporated 2019
Share capital NOK 100,000

TRAPNOR AS is registered as a limited company in Kåfjord, Troms with organisation number 824370842. The business is classified under manufacture of cordage, rope, twine and netting (NACE 13.940). The company was incorporated in 2019. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Nyutvikling av egne prototypeteiner for krabbe og fisk, produksjon/reparasjon av teiner, salg av krabbe og fisketeiner. Ta oppdrag for andre selskaper/bedrifter innen nyutvikling og produksjon av teiner og andre fiskeredskaper. Investering i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 272,000 in revenue and NOK 183,000 in operating profit.

Key figures · 2025

Revenue
NOK 272,000
Operating profit
NOK 183,000
Equity
NOK 143,000
Est. value
NOK 600,000

Financial health · 2025

Liquidity
3.34
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.5%
Good
Equity as a share of total capital

Who owns TRAPNOR AS?

PER STEINAR KARLSEN
TRAPNOR AS
NOK 272,000 rev. · NOK 183,000 profit

TRAPNOR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TRAPNOR AS

Who owns TRAPNOR AS?

PER STEINAR KARLSEN is the largest registered owner, with 60.0%.

What is the revenue of TRAPNOR AS?

TRAPNOR AS had revenue of NOK 272,000 in 2025.

Who is the general manager of TRAPNOR AS?

Per Steinar Karlsen is registered as general manager of TRAPNOR AS.

Where is TRAPNOR AS based?

TRAPNOR AS has its business address in Samuelsberg.

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.