BIZTRAC BETA
Central agencies for goods and transportation procurement

ASKER OG BÆRUM TAXI AS

Org. no. 933143384 Limited company (AS) Bærum Incorporated 1964 Active
Ownership graph ↗
Revenue 2024 NOK 193,000
Operating profit NOK −153,000
Equity NOK 17.2m
Incorporated 1964
Share capital NOK 3.5m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−153k kr).

ASKER OG BÆRUM TAXI AS is registered as a limited company in Bærum, Akershus with organisation number 933143384. The business is classified under central agencies for goods and transportation procurement (NACE 52.211). The company was incorporated in 1964. Registered share capital is NOK 3.5m, divided into 3450 shares. The company's stated purpose is: “Eie og drive eiendommen Ramstadsletta 2. samt å bistå drosjeeiere tilknyttet Asker og Bærum Taxisentral med tjenester av enhver art.”. The most recent filed accounts, for the 2024 financial year, show NOK 193,000 in revenue and NOK −153,000 in operating profit.

Key figures · 2024

Revenue
NOK 193,000
Operating profit
NOK −153,000
Equity
NOK 17.2m
Est. value
NOK 8.9m

Financial health · 2024

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

Who owns ASKER OG BÆRUM TAXI AS?

ASKER OG BÆRUM TAXI SA
ASKER OG BÆRUM TAXI AS
NOK 193,000 rev. · NOK −153,000 profit

ASKER OG BÆRUM TAXI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ASKER OG BÆRUM TAXI AS

Who owns ASKER OG BÆRUM TAXI AS?

ASKER OG BÆRUM TAXI SA is the largest registered owner, with 100.0%.

What is the revenue of ASKER OG BÆRUM TAXI AS?

ASKER OG BÆRUM TAXI AS had revenue of NOK 193,000 in 2024.

Where is ASKER OG BÆRUM TAXI AS based?

ASKER OG BÆRUM TAXI AS has its business address in Blommenholm.

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.