BIZTRAC BETA
Business and other management consultancy activities

STIM CONSULTING AS

Org. no. 934921887 Limited company (AS) Tromsø Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 469,000
Equity NOK 39,000
Incorporated 2025
Share capital NOK 30,000

STIM CONSULTING AS is registered as a limited company in Tromsø, Troms with organisation number 934921887. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Salg av konsulenttjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 469,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK 469,000
Equity
NOK 39,000
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
1.06
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
6.1%
Weak
Equity as a share of total capital

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

Who owns STIM CONSULTING AS?

STIAN JOHANSEN MÆKELÆ
STIM CONSULTING AS
NOK 1.0m rev. · NOK 469,000 profit

STIM CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Group structure

STIM CONSULTING AS er morselskap for 1 datterselskap:

Frequently asked questions about STIM CONSULTING AS

Who owns STIM CONSULTING AS?

STIAN JOHANSEN MÆKELÆ is the largest registered owner, with 100.0%.

What is the revenue of STIM CONSULTING AS?

STIM CONSULTING AS had revenue of NOK 1.0m in 2025.

Who is the general manager of STIM CONSULTING AS?

Stian Johansen Mækelæ is registered as general manager of STIM CONSULTING AS.

Where is STIM CONSULTING AS based?

STIM CONSULTING AS has its business address in Kvaløysletta.

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.