biztrac. BETA
COMPANY REGISTER PROFILE
924925779 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
On-demand passenger transport service activities by vehicle with driver

PEYMAN TAXI AS

Org. no. 924925779 Limited company (AS) Trondheim Incorporated 2020 Active
Revenue 2025 NOK 1.2m
Operating profit NOK 59,000
Equity NOK 3,000
Incorporated 2020
Share capital NOK 30,000

PEYMAN TAXI AS is registered as a limited company in Trondheim, Trøndelag with organisation number 924925779. The business is classified under on-demand passenger transport service activities by vehicle with driver (NACE 49.330). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Taxivirksomhet, samt virksomhet knyttet til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 59,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
▼ −3 %
Operating profit
NOK 59,000
▲ +209 %
Equity
NOK 3,000
▲ +107 %
Est. value
NOK 208,000

Financial health · 2025

Liquidity
0.97
Weak
Current assets ÷ current liabilities
Profitability
10.8%
Good
Return on total assets
Solidity
0.6%
Weak
Equity as a share of total capital

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

Who owns PEYMAN TAXI AS?

PEYMAN TAXI AS
NOK 1.2m rev. · NOK 59,000 profit

PEYMAN TAXI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PEYMAN TAXI AS

Who owns PEYMAN TAXI AS?

Peyman Abbasisarijlou is the largest registered owner, with 100.0%.

What is the revenue of PEYMAN TAXI AS?

PEYMAN TAXI AS had revenue of NOK 1.2m in 2025.

Who is the general manager of PEYMAN TAXI AS?

Peyman Abbasisarijlou is registered as general manager of PEYMAN TAXI AS.

Where is PEYMAN TAXI AS based?

PEYMAN TAXI AS has its business address in Leinstrand.

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.