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

ETNEDAL TAXI AS

Org. no. 929481453 Limited company (AS) Etnedal Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 4.4m
Operating profit NOK 435,000
Equity NOK 252,000
Incorporated 2022
Employees 8
Share capital NOK 30,000

ETNEDAL TAXI AS is registered as a limited company in Etnedal, Innlandet with organisation number 929481453. The business is classified under on-demand passenger transport service activities by vehicle with driver (NACE 49.330). The company was incorporated in 2022 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drive drosjetransport, organisere, administrere og formidle kontrakter, markedsføre og videreutvikle taxinæringens tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.4m in revenue and NOK 435,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.4m
Operating profit
NOK 435,000
Equity
NOK 252,000
Est. value
NOK 1.3m

Financial health · 2024

Liquidity
1.46
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.0%
Satisfactory
Equity as a share of total capital

Who owns ETNEDAL TAXI AS?

TERJE BJØRNØDEGÅRD
ETNEDAL TAXI AS
NOK 4.4m rev. · NOK 435,000 profit

ETNEDAL TAXI AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ETNEDAL TAXI AS own?

ETNEDAL TAXI AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ETNEDAL TAXI AS

Who owns ETNEDAL TAXI AS?

TERJE BJØRNØDEGÅRD is the largest registered owner, with 100.0%.

What is the revenue of ETNEDAL TAXI AS?

ETNEDAL TAXI AS had revenue of NOK 4.4m in 2024.

Where is ETNEDAL TAXI AS based?

ETNEDAL TAXI AS has its business address in Etnedal.

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.