biztrac. BETA
COMPANY REGISTER PROFILE
971235667 ORG. NO. 2025 ACCOUNTS 11 SECTIONS
Active UPDATED 03.10.2026
Temporary employment agency activities and other human resource provisions

FABI AS

Org. no. 971235667 Limited company (AS) Sandnes Incorporated 1994 Active
Ownership graph ↗
Revenue 2025 NOK 29.4m
Operating profit NOK 431,000
Equity NOK 5.9m
Incorporated 1994
Employees 31
Share capital NOK 3.2m

FABI AS is registered as a limited company in Sandnes, Rogaland with organisation number 971235667. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 1994 and has 31 registered employees. Registered share capital is NOK 3.2m, divided into 800 shares. The company's stated purpose is: “Drive konsulentvirksomhet, deltakelse i andre selskaper, investering i eiendom, forvaltning og alt som står i forbindelse hermed.”. The most recent filed accounts, for the 2025 financial year, show NOK 29.4m in revenue and NOK 431,000 in operating profit.

Former names: FABI KOMPETANSE AS

Key figures · 2025

Revenue
NOK 29.4m
▲ +23 %
Operating profit
NOK 431,000
▲ +357 %
Equity
NOK 5.9m
▼ −23 %
Est. value
NOK 4.4m

Financial health · 2025

Liquidity
1.60
Good
Current assets ÷ current liabilities
Profitability
3.6%
Weak
Return on total assets
Solidity
32.1%
Good
Equity as a share of total capital

Who owns FABI AS?

FABI AS
NOK 29.4m rev. · NOK 431,000 profit

FABI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FABI AS

Who owns FABI AS?

PLATINA AS is the largest registered owner, with 100.0%.

What is the revenue of FABI AS?

FABI AS had revenue of NOK 29.4m in 2025.

Who is the general manager of FABI AS?

Trine Johnsen Vigorito is registered as general manager of FABI AS.

Where is FABI AS based?

FABI AS has its business address in Sandnes.

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.