biztrac. BETA
COMPANY REGISTER PROFILE
971333650 ORG. NO. 2023 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other educational support services n.e.c.

FAGOPPLÆRING SYD

Org. no. 971333650 Association/club/organisation (FLI) Lindesnes Incorporated 1994 Active
Ownership graph ↗
Revenue 2023 NOK 14.2m
Operating profit NOK −583,000
Equity NOK 4.4m
Incorporated 1994
Employees 10

Signals

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

FAGOPPLÆRING SYD is registered as a association/club/organisation in Lindesnes, Agder with organisation number 971333650. The business is classified under other educational support services n.e.c. (NACE 85.699). The company was incorporated in 1994 and has 10 registered employees. The most recent filed accounts, for the 2023 financial year, show NOK 14.2m in revenue and NOK −583,000 in operating profit.

Former names: OFIM - OPPLÆRINGSRINGEN FOR INDUSTRIFAG I MANDALSREG., OPPLÆRINGSRINGEN FOR INDUSTRIFAG I MANDALSREGIONEN OFIM, OPPLÆRINGSKONTORET FOR INDUSTRIFAG I MANDALSREGIONEN OFIM, FAGOPPLÆRING SØR

Key figures · 2023

Revenue
NOK 14.2m
Operating profit
NOK −583,000
Equity
NOK 4.4m
Est. value
NOK 14.7m

Financial health · 2023

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

Who owns FAGOPPLÆRING SYD?

No shareholders are registered for FAGOPPLÆRING SYD in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about FAGOPPLÆRING SYD

What is the revenue of FAGOPPLÆRING SYD?

FAGOPPLÆRING SYD had revenue of NOK 14.2m in 2023.

Who is the general manager of FAGOPPLÆRING SYD?

Åse Michaelsen is registered as general manager of FAGOPPLÆRING SYD.

Where is FAGOPPLÆRING SYD based?

FAGOPPLÆRING SYD has its business address in Mandal.

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.