BIZTRAC BETA
Finishing of textiles

KERN PROFILERING AS

Org. no. 886402112 Limited company (AS) Ulstein Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 12,000
Equity NOK 482,000
Incorporated 2003
Share capital NOK 100,000

KERN PROFILERING AS is registered as a limited company in Ulstein, Møre og Romsdal with organisation number 886402112. The business is classified under finishing of textiles (NACE 13.300). The company was incorporated in 2003. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Produksjon direkte og indirekte på tekstiler. Reklame, silketrykk, skilter, dekor, aksidens etc., herunder kunne yte bistand til liknende selskap. Videre skal selskapet kunne investere i andre selskaper med økonomisk gevinst som formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 12,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK 12,000
Equity
NOK 482,000
Est. value
NOK 301,000

Financial health · 2025

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

Who owns KERN PROFILERING AS?

BJØRNAR KERN
KERN PROFILERING AS
NOK 1.6m rev. · NOK 12,000 profit

KERN PROFILERING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KERN PROFILERING AS

Who owns KERN PROFILERING AS?

BJØRNAR KERN is the largest registered owner, with 70.2%.

What is the revenue of KERN PROFILERING AS?

KERN PROFILERING AS had revenue of NOK 1.6m in 2025.

Who is the general manager of KERN PROFILERING AS?

Bjørnar Kern is registered as general manager of KERN PROFILERING AS.

Where is KERN PROFILERING AS based?

KERN PROFILERING AS has its business address in Ulsteinvik.

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.