BIZTRAC BETA
Activities of adventure companies

NORWEGIAN SPEED FACTORY AS

Org. no. 917062994 Limited company (AS) Enebakk Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 114,000
Operating profit NOK 61,000
Equity NOK 146,000
Incorporated 2016
Share capital NOK 30,000

NORWEGIAN SPEED FACTORY AS is registered as a limited company in Enebakk, Akershus with organisation number 917062994. The business is classified under activities of adventure companies (NACE 93.291). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kurs og event (opplevelsesaktiviteter) innen kjøring og sikkerhet. Samt utleie av arbeidskraft og bemanning.”. The most recent filed accounts, for the 2024 financial year, show NOK 114,000 in revenue and NOK 61,000 in operating profit.

Key figures · 2024

Revenue
NOK 114,000
Operating profit
NOK 61,000
Equity
NOK 146,000
Est. value
NOK 269,000

Financial health · 2024

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

Who owns NORWEGIAN SPEED FACTORY AS?

ØISTEIN SARIBERGET
NORWEGIAN SPEED FACTORY AS
NOK 114,000 rev. · NOK 61,000 profit

NORWEGIAN SPEED FACTORY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORWEGIAN SPEED FACTORY AS

Who owns NORWEGIAN SPEED FACTORY AS?

ØISTEIN SARIBERGET is the largest registered owner, with 100.0%.

What is the revenue of NORWEGIAN SPEED FACTORY AS?

NORWEGIAN SPEED FACTORY AS had revenue of NOK 114,000 in 2024.

Who is the general manager of NORWEGIAN SPEED FACTORY AS?

Øistein Sariberget is registered as general manager of NORWEGIAN SPEED FACTORY AS.

Where is NORWEGIAN SPEED FACTORY AS based?

NORWEGIAN SPEED FACTORY AS has its business address in Enebakk.

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.