biztrac. BETA
COMPANY REGISTER PROFILE
914975689 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
General primary education

HALSNØY FRISKULE AS

Org. no. 914975689 Limited company (AS) Kvinnherad Incorporated 2014 Active
Revenue 2025 NOK 0
Operating profit NOK −1,000
Equity NOK 22,000
Incorporated 2014
Share capital NOK 54,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1k kr).

HALSNØY FRISKULE AS is registered as a limited company in Kvinnherad, Vestland with organisation number 914975689. The business is classified under general primary education (NACE 85.201). The company was incorporated in 2014. Registered share capital is NOK 54,000, divided into 54 shares. The company's stated purpose is: “Driva undervisning bygd på det kristne verdigrunnlaget. Skulen skal gje opplæring i samsvar med privatskulelova, herunder leiga/eiga tenelege lokalar til føremålet. Selskapet har ikkje som økonomisk føremål å gje utbytte til eigarane.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −1,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −1,000
Equity
NOK 22,000
▼ −10 %
Est. value
NOK 31,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-5.2%
Not satisfactory
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HALSNØY FRISKULE AS?

No shareholders are registered for HALSNØY FRISKULE AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about HALSNØY FRISKULE AS

What is the revenue of HALSNØY FRISKULE AS?

HALSNØY FRISKULE AS had revenue of NOK 0 in 2025.

Where is HALSNØY FRISKULE AS based?

HALSNØY FRISKULE AS has its business address in Sæbøvik.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.