BIZTRAC BETA
Temporary employment agency activities and other human resource provisions

STIMA BYGG AS

Org. no. 891398522 Limited company (AS) Rælingen Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 39.0m
Operating profit NOK −11.2m
Equity NOK −9.9m
Incorporated 2007
Employees 8
Share capital NOK 200,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−9,9 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−11,2 mill kr).

STIMA BYGG AS is registered as a limited company in Rælingen, Akershus with organisation number 891398522. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2007 and has 8 registered employees. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Eiendomsutvikling og oppføring og salg av boliger, samt alt som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 39.0m in revenue and NOK −11.2m in operating profit.

Key figures · 2024

Revenue
NOK 39.0m
Operating profit
NOK −11.2m
Equity
NOK −9.9m

Financial health · 2024

Liquidity
1.66
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-49.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns STIMA BYGG AS?

STIMA AS
STIMA BYGG AS
NOK 39.0m rev. · NOK −11.2m profit

STIMA BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STIMA BYGG AS

Who owns STIMA BYGG AS?

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

What is the revenue of STIMA BYGG AS?

STIMA BYGG AS had revenue of NOK 39.0m in 2024.

Where is STIMA BYGG AS based?

STIMA BYGG AS has its business address in Fjerdingby.

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.