BIZTRAC BETA
Other educational support services n.e.c.

BILFAGENES OPPLÆRINGSKONTOR STORD AS

Org. no. 979143834 Limited company (AS) Stord Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 444,000
Operating profit NOK 19,000
Equity NOK 1.4m
Incorporated 1997
Share capital NOK 100,000

BILFAGENES OPPLÆRINGSKONTOR STORD AS is registered as a limited company in Stord, Vestland with organisation number 979143834. The business is classified under other educational support services n.e.c. (NACE 85.699). The company was incorporated in 1997. Registered share capital is NOK 100,000, divided into 70 shares. The company's stated purpose is: “Bistå medlemsbedrifter med opplæring i bilfagene etter lov om fagopplæring i arbeidslivet.”. The most recent filed accounts, for the 2024 financial year, show NOK 444,000 in revenue and NOK 19,000 in operating profit.

Key figures · 2024

Revenue
NOK 444,000
Operating profit
NOK 19,000
Equity
NOK 1.4m
Est. value
NOK 872,000

Financial health · 2024

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

Who owns BILFAGENES OPPLÆRINGSKONTOR STORD AS?

No shareholders are registered for BILFAGENES OPPLÆRINGSKONTOR STORD AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about BILFAGENES OPPLÆRINGSKONTOR STORD AS

What is the revenue of BILFAGENES OPPLÆRINGSKONTOR STORD AS?

BILFAGENES OPPLÆRINGSKONTOR STORD AS had revenue of NOK 444,000 in 2024.

Who is the general manager of BILFAGENES OPPLÆRINGSKONTOR STORD AS?

Vidar Eide Bjelland is registered as general manager of BILFAGENES OPPLÆRINGSKONTOR STORD AS.

Where is BILFAGENES OPPLÆRINGSKONTOR STORD AS based?

BILFAGENES OPPLÆRINGSKONTOR STORD AS has its business address in Stord.

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.