biztrac. BETA
COMPANY REGISTER PROFILE
834140942 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Freight transport by road

STREAM AS

Org. no. 834140942 Limited company (AS) Bærum Incorporated 2024 Active
Revenue 2025 NOK 2.2m
Operating profit NOK 87,000
Equity NOK 94,000
Incorporated 2024
Employees 5
Share capital NOK 30,000

STREAM AS is registered as a limited company in Bærum, Akershus with organisation number 834140942. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2024 and has 5 registered employees. 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 2.2m in revenue and NOK 87,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK 87,000
Equity
NOK 94,000
▲ +287 %
Est. value
NOK 327,000

Financial health · 2025

Liquidity
1.29
Satisfactory
Current assets ÷ current liabilities
Profitability
56.6%
Very good
Return on total assets
Solidity
32.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns STREAM AS?

STREAM AS
NOK 2.2m rev. · NOK 87,000 profit

STREAM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STREAM AS

Who owns STREAM AS?

Ahmad Mazen Khateeb is the largest registered owner, with 100.0%.

What is the revenue of STREAM AS?

STREAM AS had revenue of NOK 2.2m in 2025.

Who is the general manager of STREAM AS?

Ahmad Mazen Khateeb is registered as general manager of STREAM AS.

Where is STREAM AS based?

STREAM AS has its business address in Lommedalen.

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.