biztrac. BETA
COMPANY REGISTER PROFILE
983984630 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Site preparation

E OLSEN TRANSPORT AS

Org. no. 983984630 Limited company (AS) Verdal Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 12.0m
Operating profit NOK 175,000
Equity NOK 1.5m
Incorporated 2001
Employees 6
Share capital NOK 100,000

E OLSEN TRANSPORT AS is registered as a limited company in Verdal, Trøndelag with organisation number 983984630. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2001 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg av masse og transport og alt hva dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.0m in revenue and NOK 175,000 in operating profit.

Key figures · 2025

Revenue
NOK 12.0m
▼ −7 %
Operating profit
NOK 175,000
▼ −84 %
Equity
NOK 1.5m
▲ +10 %
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
1.95
Good
Current assets ÷ current liabilities
Profitability
6.2%
Satisfactory
Return on total assets
Solidity
48.4%
Very good
Equity as a share of total capital

Who owns E OLSEN TRANSPORT AS?

E OLSEN TRANSPORT AS
NOK 12.0m rev. · NOK 175,000 profit

E OLSEN TRANSPORT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about E OLSEN TRANSPORT AS

Who owns E OLSEN TRANSPORT AS?

Even Olsen is the largest registered owner, with 80.0%.

What is the revenue of E OLSEN TRANSPORT AS?

E OLSEN TRANSPORT AS had revenue of NOK 12.0m in 2025.

Who is the general manager of E OLSEN TRANSPORT AS?

Even Olsen is registered as general manager of E OLSEN TRANSPORT AS.

Where is E OLSEN TRANSPORT AS based?

E OLSEN TRANSPORT AS has its business address in Verdal.

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.