BIZTRAC BETA
Computer programming activities

HOMESOURCING AS

Org. no. 924468505 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 32.1m
Operating profit NOK 1.4m
Equity NOK 3.6m
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-04-17 Adresseendring registrert 2026-04-17.

HOMESOURCING AS is registered as a limited company in Oslo, Oslo with organisation number 924468505. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utleie av konsulenter i Europa for norske bedrifter ved bruk av en hybridmodell basert på on-site og remote.”. The most recent filed accounts, for the 2024 financial year, show NOK 32.1m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 32.1m
Operating profit
NOK 1.4m
Equity
NOK 3.6m
Est. value
NOK 9.8m

Financial health · 2024

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

Who owns HOMESOURCING AS?

FJELSTAD AS
HOMESOURCING AS
NOK 32.1m rev. · NOK 1.4m profit

HOMESOURCING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does HOMESOURCING AS own?

HOMESOURCING AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about HOMESOURCING AS

Who owns HOMESOURCING AS?

FJELSTAD AS is the largest registered owner, with 70.2%.

What is the revenue of HOMESOURCING AS?

HOMESOURCING AS had revenue of NOK 32.1m in 2024.

Who is the general manager of HOMESOURCING AS?

Espen Lippert is registered as general manager of HOMESOURCING AS.

Where is HOMESOURCING AS based?

HOMESOURCING AS has its business address in Oslo.

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.