BIZTRAC BETA
Freight transport by road

E.ANGELTVEDT TRANSPORT AS

Org. no. 932755874 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 3.3m
Operating profit NOK 2.1m
Equity NOK 1.7m
Incorporated 2023
Share capital NOK 30,000

E.ANGELTVEDT TRANSPORT AS is registered as a limited company in Bergen, Vestland with organisation number 932755874. 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: “Selge varer og tjenester innen godstransport på vei og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK 2.1m in operating profit.

Key figures · 2025

Revenue
NOK 3.3m
Operating profit
NOK 2.1m
Equity
NOK 1.7m
Est. value
NOK 7.2m

Financial health · 2024

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

Who owns E.ANGELTVEDT TRANSPORT AS?

EIRIK ANGELTVEDT
E.ANGELTVEDT TRANSPORT AS
NOK 3.3m rev. · NOK 2.1m profit

E.ANGELTVEDT TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about E.ANGELTVEDT TRANSPORT AS

Who owns E.ANGELTVEDT TRANSPORT AS?

EIRIK ANGELTVEDT is the largest registered owner, with 100.0%.

What is the revenue of E.ANGELTVEDT TRANSPORT AS?

E.ANGELTVEDT TRANSPORT AS had revenue of NOK 3.3m in 2025.

Who is the general manager of E.ANGELTVEDT TRANSPORT AS?

Eirik Angeltvedt is registered as general manager of E.ANGELTVEDT TRANSPORT AS.

Where is E.ANGELTVEDT TRANSPORT AS based?

E.ANGELTVEDT TRANSPORT AS has its business address in Nyborg.

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.