BIZTRAC BETA
Industrial product and fashion design activities

KOFFERNOR AS

Org. no. 932211130 Limited company (AS) Trondheim Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 134,000
Operating profit NOK 126,000
Equity NOK 161,000
Incorporated 2023
Share capital NOK 40,000

KOFFERNOR AS is registered as a limited company in Trondheim, Trøndelag with organisation number 932211130. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2023. Registered share capital is NOK 40,000, divided into 40000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2024 financial year, show NOK 134,000 in revenue and NOK 126,000 in operating profit.

Key figures · 2024

Revenue
NOK 134,000
Operating profit
NOK 126,000
Equity
NOK 161,000
Est. value
NOK 514,000

Financial health · 2024

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

Who owns KOFFERNOR AS?

KRISTOFFER NORLI
KOFFERNOR AS
NOK 134,000 rev. · NOK 126,000 profit

KOFFERNOR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KOFFERNOR AS own?

KOFFERNOR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KOFFERNOR AS

Who owns KOFFERNOR AS?

KRISTOFFER NORLI is the largest registered owner, with 100.0%.

What is the revenue of KOFFERNOR AS?

KOFFERNOR AS had revenue of NOK 134,000 in 2024.

Where is KOFFERNOR AS based?

KOFFERNOR AS has its business address in Trondheim.

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.