BIZTRAC BETA
COMPANY REGISTER PROFILE
980846490 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Marine fishing

AMALIK AS

Org. no. 980846490 Limited company (AS) Stad Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −26,000
Equity NOK 143,000
Incorporated 1999
Share capital NOK 103,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−26k kr).

AMALIK AS is registered as a limited company in Stad, Vestland with organisation number 980846490. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 1999. Registered share capital is NOK 103,000, divided into 3442 shares. The company's stated purpose is: “Investering i aksjer og verdipapirer, samt delta i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −26,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −26,000
Equity
NOK 143,000
Est. value
NOK 136,000

Financial health · 2025

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

Who owns AMALIK AS?

KJELL INGOLF RUNDEREIM
AMALIK AS
NOK 0 rev. · NOK −26,000 profit

AMALIK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does AMALIK AS own?

AMALIK AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about AMALIK AS

Who owns AMALIK AS?

KJELL INGOLF RUNDEREIM is the largest registered owner, with 100.0%.

What is the revenue of AMALIK AS?

AMALIK AS had revenue of NOK 0 in 2025.

Who is the general manager of AMALIK AS?

Kjell Ingolf Rundereim is registered as general manager of AMALIK AS.

Where is AMALIK AS based?

AMALIK AS has its business address in Flatraket.

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.