BIZTRAC BETA
Business and other management consultancy activities

STIBRA CONSULTING AS

Org. no. 936574718 Limited company (AS) Hareid Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 11,000
Operating profit NOK 7,000
Equity NOK 30,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-10-27.

STIBRA CONSULTING AS is registered as a limited company in Hareid, Møre og Romsdal with organisation number 936574718. 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 30 shares. The company's stated purpose is: “Bedriftsrågivning.”. The most recent filed accounts, for the 2025 financial year, show NOK 11,000 in revenue and NOK 7,000 in operating profit.

Key figures · 2025

Revenue
NOK 11,000
Operating profit
NOK 7,000
Equity
NOK 30,000
Est. value
NOK 42,000

Financial health · 2025

Liquidity
10.01
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
90.0%
Weak
Equity as a share of total capital

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

Who owns STIBRA CONSULTING AS?

STIG OLAV BRAUTASET
STIBRA CONSULTING AS
NOK 11,000 rev. · NOK 7,000 profit

STIBRA CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STIBRA CONSULTING AS

Who owns STIBRA CONSULTING AS?

STIG OLAV BRAUTASET is the largest registered owner, with 100.0%.

What is the revenue of STIBRA CONSULTING AS?

STIBRA CONSULTING AS had revenue of NOK 11,000 in 2025.

Who is the general manager of STIBRA CONSULTING AS?

Stig Olav Brautaset is registered as general manager of STIBRA CONSULTING AS.

Where is STIBRA CONSULTING AS based?

STIBRA CONSULTING AS has its business address in Hareid.

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.