biztrac. BETA
COMPANY REGISTER PROFILE
994318365 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Freight ocean transport

AWILCO SHIPPING AS

Org. no. 994318365 Limited company (AS) Oslo Incorporated 2009 Active
Operating profit NOK −48,000
Equity NOK 11.9m
Incorporated 2009
Share capital NOK 100,000

Signals

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

AWILCO SHIPPING AS is registered as a limited company in Oslo, Oslo with organisation number 994318365. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 10000 shares. The company's stated purpose is: “Skipsfart og derved beslektet virksomhet. Innenfor formålet er også erverv, forvaltning, belåning og salg av kapitalgjenstander innenfor shippingvirksomhet, samt investering i aksjer, obligasjoner og interessentinnskudd av enhver art knyttet til skipsfart, og deltakelse med eierinteresser i andre shippingselskaper, samt naturlig tilhørende virksomhet.”.

Key figures · 2025

Operating profit
NOK −48,000
▲ +25 %
Equity
NOK 11.9m
▲ +4 %
Est. value
NOK 8.6m

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
4.0%
Weak
Return on total assets
Solidity
100.0%
Very good
Equity as a share of total capital

Who owns AWILCO SHIPPING AS?

AWILCO SHIPPING AS
· NOK −48,000 profit

AWILCO SHIPPING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AWILCO SHIPPING AS

Who owns AWILCO SHIPPING AS?

AWILCO AS is the largest registered owner, with 100.0%.

Who is the general manager of AWILCO SHIPPING AS?

Jens-Julius Ramdahl Nygaard is registered as general manager of AWILCO SHIPPING AS.

Where is AWILCO SHIPPING AS based?

AWILCO SHIPPING AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.