BIZTRAC BETA
General primary education

BRYGGJA SKULE AS

Org. no. 920314767 Limited company (AS) Stad Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 8.3m
Operating profit NOK 173,000
Equity NOK 1.0m
Incorporated 2018
Employees 15
Share capital NOK 316,000

BRYGGJA SKULE AS is registered as a limited company in Stad, Vestland with organisation number 920314767. The business is classified under general primary education (NACE 85.201). The company was incorporated in 2018 and has 15 registered employees. Registered share capital is NOK 316,000, divided into 31600 shares. The company's stated purpose is: “Undervising bygt på eit kristent verdigrunnlag og førestå anna drift som står i samband med dette. Selskapet kan i tillegg eige skuleeigedom og drive Skulefritidsordning (SFO) som tilleggsverksemd ved skulen. Skulen skal gje opplæring i samsvar med Friskulelova (Lov om Friskole) og Opplæringslova, med tilhøyrande forskrifter.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.3m in revenue and NOK 173,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.3m
Operating profit
NOK 173,000
Equity
NOK 1.0m
Est. value
NOK 1.4m

Financial health · 2024

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

Who owns BRYGGJA SKULE AS?

No shareholders are registered for BRYGGJA SKULE AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about BRYGGJA SKULE AS

What is the revenue of BRYGGJA SKULE AS?

BRYGGJA SKULE AS had revenue of NOK 8.3m in 2024.

Who is the general manager of BRYGGJA SKULE AS?

Torgeir Hole is registered as general manager of BRYGGJA SKULE AS.

Where is BRYGGJA SKULE AS based?

BRYGGJA SKULE AS has its business address in Bryggja.

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.