BIZTRAC BETA
Temporary employment agency activities and other human resource provisions

WIISDA AS

Org. no. 992707577 Limited company (AS) Bergen Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 52.4m
Operating profit NOK 1.4m
Equity NOK 2.4m
Incorporated 2008
Employees 32
Share capital NOK 200,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

WIISDA AS is registered as a limited company in Bergen, Vestland with organisation number 992707577. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2008 and has 32 registered employees. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Utleie av utenlandsk arbeidskraft til bedrifter samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 52.4m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 52.4m
Operating profit
NOK 1.4m
Equity
NOK 2.4m
Est. value
NOK 6.8m

Financial health · 2024

Liquidity
1.13
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.1%
Good
Equity as a share of total capital

Who owns WIISDA AS?

H B Invest AS
WIISDA AS
NOK 52.4m rev. · NOK 1.4m profit

WIISDA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WIISDA AS

Who owns WIISDA AS?

H B Invest AS is the largest registered owner, with 100.0%.

What is the revenue of WIISDA AS?

WIISDA AS had revenue of NOK 52.4m in 2024.

Who is the general manager of WIISDA AS?

Erik Bergsland is registered as general manager of WIISDA AS.

Where is WIISDA AS based?

WIISDA AS has its business address in Nyborg.

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.