BIZTRAC BETA
Other support activities for transportation

BYBERG SHIPPING AS

Org. no. 993930997 Limited company (AS) Lillestrøm Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK −13,000
Equity NOK 5.7m
Incorporated 2009
Share capital NOK 100,000

Signals

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

BYBERG SHIPPING AS is registered as a limited company in Lillestrøm, Akershus with organisation number 993930997. The business is classified under other support activities for transportation (NACE 52.260). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Transportformidling, konsulenttjenester, logistikk, samt hva som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
Operating profit
NOK −13,000
Equity
NOK 5.7m
Est. value
NOK 5.0m

Financial health · 2025

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

Who owns BYBERG SHIPPING AS?

EGIL BYBERG HANSEN
BYBERG SHIPPING AS
NOK 2.5m rev. · NOK −13,000 profit

BYBERG SHIPPING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BYBERG SHIPPING AS

Who owns BYBERG SHIPPING AS?

EGIL BYBERG HANSEN is the largest registered owner, with 100.0%.

What is the revenue of BYBERG SHIPPING AS?

BYBERG SHIPPING AS had revenue of NOK 2.5m in 2025.

Who is the general manager of BYBERG SHIPPING AS?

Egil Byberg Hansen is registered as general manager of BYBERG SHIPPING AS.

Where is BYBERG SHIPPING AS based?

BYBERG SHIPPING AS has its business address in Lillestrøm.

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.