biztrac. BETA
COMPANY REGISTER PROFILE
975801896 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Post-secondary non-tertiary education

FAGSKOLEN FOR BOKBRANSJEN STI

Org. no. 975801896 Foundation (STI) Oslo Incorporated 1995 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK −237,000
Equity NOK 1.4m
Incorporated 1995
Share capital NOK 100,000

Signals

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

FAGSKOLEN FOR BOKBRANSJEN STI is registered as a foundation in Oslo, Oslo with organisation number 975801896. The business is classified under post-secondary non-tertiary education (NACE 85.330). The company was incorporated in 1995. Registered share capital is NOK 100,000. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK −237,000 in operating profit.

Former names: STIFTELSEN FAGSKOLEN FOR BOK OG PAPIR

Key figures · 2025

Revenue
NOK 2.3m
▲ +4 %
Operating profit
NOK −237,000
▼ −978 %
Equity
NOK 1.4m
▼ −10 %
Est. value
NOK 2.8m

Financial health · 2025

Liquidity
3.43
Very good
Current assets ÷ current liabilities
Profitability
-7.3%
Not satisfactory
Return on total assets
Solidity
70.8%
Very good
Equity as a share of total capital

Who owns FAGSKOLEN FOR BOKBRANSJEN STI?

No shareholders are registered for FAGSKOLEN FOR BOKBRANSJEN STI in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about FAGSKOLEN FOR BOKBRANSJEN STI

What is the revenue of FAGSKOLEN FOR BOKBRANSJEN STI?

FAGSKOLEN FOR BOKBRANSJEN STI had revenue of NOK 2.3m in 2025.

Who is the general manager of FAGSKOLEN FOR BOKBRANSJEN STI?

Cecilie Brun Løwe is registered as general manager of FAGSKOLEN FOR BOKBRANSJEN STI.

Where is FAGSKOLEN FOR BOKBRANSJEN STI based?

FAGSKOLEN FOR BOKBRANSJEN STI has its business address in Oslo.

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.