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

HEIMSTAD AS

Org. no. 990879958 Limited company (AS) Nord-Fron Incorporated 2006 Active
Revenue 2025 NOK 0
Operating profit NOK −26,000
Equity NOK 1.2m
Incorporated 2006
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−26k kr).

HEIMSTAD AS is registered as a limited company in Nord-Fron, Innlandet with organisation number 990879958. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2006. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Investere i omløps og anleggsmidler, samt utleie av arbeidskraft.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −26,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −26,000
▼ −457 %
Equity
NOK 1.2m
▼ −1 %
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
7.58
Very good
Current assets ÷ current liabilities
Profitability
-0.5%
Not satisfactory
Return on total assets
Solidity
95.6%
Very good
Equity as a share of total capital

Who owns HEIMSTAD AS?

HEIMSTAD AS
NOK 0 rev. · NOK −26,000 profit

HEIMSTAD AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HEIMSTAD AS own?

HEIMSTAD AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HEIMSTAD AS

Who owns HEIMSTAD AS?

Simen Killi is the largest registered owner, with 100.0%.

What is the revenue of HEIMSTAD AS?

HEIMSTAD AS had revenue of NOK 0 in 2025.

Where is HEIMSTAD AS based?

HEIMSTAD AS has its business address in Kvam.

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.