BIZTRAC BETA
Central agencies for goods and transportation procurement

SELBU DROSJESENTRAL AS

Org. no. 921133014 Limited company (AS) Selbu Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 2.5m
Operating profit NOK 165,000
Equity NOK 473,000
Incorporated 2018
Employees 5
Share capital NOK 150,000

SELBU DROSJESENTRAL AS is registered as a limited company in Selbu, Trøndelag with organisation number 921133014. The business is classified under central agencies for goods and transportation procurement (NACE 52.211). The company was incorporated in 2018 and has 5 registered employees. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Drive drosjetransport samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.5m in revenue and NOK 165,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.5m
Operating profit
NOK 165,000
Equity
NOK 473,000
Est. value
NOK 644,000

Financial health · 2024

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

Who owns SELBU DROSJESENTRAL AS?

JOHN-ERIK STAMNES STORNES
SELBU DROSJESENTRAL AS
NOK 2.5m rev. · NOK 165,000 profit

SELBU DROSJESENTRAL AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SELBU DROSJESENTRAL AS

Who owns SELBU DROSJESENTRAL AS?

JOHN-ERIK STAMNES STORNES is the largest registered owner, with 33.3%.

What is the revenue of SELBU DROSJESENTRAL AS?

SELBU DROSJESENTRAL AS had revenue of NOK 2.5m in 2024.

Who is the general manager of SELBU DROSJESENTRAL AS?

Kristian Stokke is registered as general manager of SELBU DROSJESENTRAL AS.

Where is SELBU DROSJESENTRAL AS based?

SELBU DROSJESENTRAL AS has its business address in Selbu.

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.