BIZTRAC BETA
On-demand passenger transport service activities by vehicle with driver

HALLSET TAXI AS

Org. no. 820465512 Limited company (AS) Trondheim Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 823,000
Operating profit NOK 70,000
Equity NOK 296,000
Incorporated 2018
Share capital NOK 30,000

HALLSET TAXI AS is registered as a limited company in Trondheim, Trøndelag with organisation number 820465512. The business is classified under on-demand passenger transport service activities by vehicle with driver (NACE 49.330). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Drosjebiltransport. Bestilling og formidling av taxioppdrag, herunder inngå kontrakter, markedsføre og videreutvikle taxinæringens tjenester, samt deltakelse i selskap med lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 823,000 in revenue and NOK 70,000 in operating profit.

Key figures · 2025

Revenue
NOK 823,000
Operating profit
NOK 70,000
Equity
NOK 296,000
Est. value
NOK 313,000

Financial health · 2025

Liquidity
1.75
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
26.4%
Good
Equity as a share of total capital

Who owns HALLSET TAXI AS?

YAGHOUB BABRI
HALLSET TAXI AS
NOK 823,000 rev. · NOK 70,000 profit

HALLSET TAXI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HALLSET TAXI AS

Who owns HALLSET TAXI AS?

YAGHOUB BABRI is the largest registered owner, with 100.0%.

What is the revenue of HALLSET TAXI AS?

HALLSET TAXI AS had revenue of NOK 823,000 in 2025.

Who is the general manager of HALLSET TAXI AS?

Yaghoub Babri is registered as general manager of HALLSET TAXI AS.

Where is HALLSET TAXI AS based?

HALLSET TAXI AS has its business address in Trondheim.

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.