BIZTRAC BETA
Freight transport by road

ZIPPY BUD & TRANSPORT SERVICE AS

Org. no. 931920421 Limited company (AS) Lørenskog Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 761,000
Operating profit NOK 35,000
Equity NOK 185,000
Incorporated 2023
Share capital NOK 30,000

ZIPPY BUD & TRANSPORT SERVICE AS is registered as a limited company in Lørenskog, Akershus with organisation number 931920421. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Gods- og varetransport på vei.”. The most recent filed accounts, for the 2024 financial year, show NOK 761,000 in revenue and NOK 35,000 in operating profit.

Key figures · 2024

Revenue
NOK 761,000
Operating profit
NOK 35,000
Equity
NOK 185,000
Est. value
NOK 227,000

Financial health · 2024

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

Who owns ZIPPY BUD & TRANSPORT SERVICE AS?

ERIK BERNTSEN
ZIPPY BUD & TRANSPORT SERVICE AS
NOK 761,000 rev. · NOK 35,000 profit

ZIPPY BUD & TRANSPORT SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ZIPPY BUD & TRANSPORT SERVICE AS

Who owns ZIPPY BUD & TRANSPORT SERVICE AS?

ERIK BERNTSEN is the largest registered owner, with 100.0%.

What is the revenue of ZIPPY BUD & TRANSPORT SERVICE AS?

ZIPPY BUD & TRANSPORT SERVICE AS had revenue of NOK 761,000 in 2024.

Who is the general manager of ZIPPY BUD & TRANSPORT SERVICE AS?

Erik Berntsen is registered as general manager of ZIPPY BUD & TRANSPORT SERVICE AS.

Where is ZIPPY BUD & TRANSPORT SERVICE AS based?

ZIPPY BUD & TRANSPORT SERVICE AS has its business address in Lørenskog.

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.