BIZTRAC BETA
Manufacture of ice cream and other edible ice

MR. ICEMAN AS

Org. no. 988953202 Limited company (AS) Nes Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 51.5m
Operating profit NOK 1.8m
Equity NOK 1.4m
Incorporated 2005
Employees 15
Share capital NOK 300,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MR. ICEMAN AS is registered as a limited company in Nes, Akershus with organisation number 988953202. The business is classified under manufacture of ice cream and other edible ice (NACE 10.520). The company was incorporated in 2005 and has 15 registered employees. Registered share capital is NOK 300,000, divided into 3000 shares. The company's stated purpose is: “Produksjon, import og salg av drikkevarer, is og andre næringsmidler samt handel og alt som står i forbindelse hermed.”. The most recent filed accounts, for the 2024 financial year, show NOK 51.5m in revenue and NOK 1.8m in operating profit.

Key figures · 2024

Revenue
NOK 51.5m
Operating profit
NOK 1.8m
Equity
NOK 1.4m
Est. value
NOK 5.7m

Financial health · 2024

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

Who owns MR. ICEMAN AS?

ICE XVII AS
MR. ICEMAN AS
NOK 51.5m rev. · NOK 1.8m profit

MR. ICEMAN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MR. ICEMAN AS

Who owns MR. ICEMAN AS?

ICE XVII AS is the largest registered owner, with 100.0%.

What is the revenue of MR. ICEMAN AS?

MR. ICEMAN AS had revenue of NOK 51.5m in 2024.

Who is the general manager of MR. ICEMAN AS?

Jack Andre Stensland is registered as general manager of MR. ICEMAN AS.

Where is MR. ICEMAN AS based?

MR. ICEMAN AS has its business address in Oppaker.

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.