BIZTRAC BETA
Activities of employment placement agencies

SKILLHOUSE AS

Org. no. 984566840 Limited company (AS) Trondheim Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 4.1m
Operating profit NOK 422,000
Equity NOK 650,000
Incorporated 2002
Employees 5
Share capital NOK 571,000

SKILLHOUSE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 984566840. The business is classified under activities of employment placement agencies (NACE 78.100). The company was incorporated in 2002 and has 5 registered employees. Registered share capital is NOK 571,000, divided into 571428 shares. The company's stated purpose is: “Rekruttering, formidling, utleie av arbeidskraft, konsulentvirksomhet, bedriftsrådgivning, og annen tjenesteytende virksomhet og alt som står i forbindelse med dette, herunder å eie aksjer i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.1m in revenue and NOK 422,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.1m
Operating profit
NOK 422,000
Equity
NOK 650,000
Est. value
NOK 2.1m

Financial health · 2025

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

Who owns SKILLHOUSE AS?

STAKEHOUSE HOLDING AS
SKILLHOUSE AS
NOK 4.1m rev. · NOK 422,000 profit

SKILLHOUSE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SKILLHOUSE AS

Who owns SKILLHOUSE AS?

STAKEHOUSE HOLDING AS is the largest registered owner, with 70.0%.

What is the revenue of SKILLHOUSE AS?

SKILLHOUSE AS had revenue of NOK 4.1m in 2025.

Who is the general manager of SKILLHOUSE AS?

Jarl Julian Espnes Bulling is registered as general manager of SKILLHOUSE AS.

Where is SKILLHOUSE AS based?

SKILLHOUSE AS has its business address in Ranheim.

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.