BIZTRAC BETA
Business and other management consultancy activities

BRAATA VERKTØY AS

Org. no. 935746639 Limited company (AS) Ringerike Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 462,000
Operating profit NOK −27,000
Equity NOK −3,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−3k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−27k kr).

BRAATA VERKTØY AS is registered as a limited company in Ringerike, Buskerud with organisation number 935746639. 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 30000 shares. The company's stated purpose is: “Å jobbe for verktøyprodusenter med å øke salget i Norge. Kundeoppfølging, verktøy-trening og messe aktiviteter.”. The most recent filed accounts, for the 2025 financial year, show NOK 462,000 in revenue and NOK −27,000 in operating profit.

Key figures · 2025

Revenue
NOK 462,000
Operating profit
NOK −27,000
Equity
NOK −3,000

Financial health · 2025

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

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

Who owns BRAATA VERKTØY AS?

STIAN BRAATA
BRAATA VERKTØY AS
NOK 462,000 rev. · NOK −27,000 profit

BRAATA VERKTØY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRAATA VERKTØY AS

Who owns BRAATA VERKTØY AS?

STIAN BRAATA is the largest registered owner, with 100.0%.

What is the revenue of BRAATA VERKTØY AS?

BRAATA VERKTØY AS had revenue of NOK 462,000 in 2025.

Where is BRAATA VERKTØY AS based?

BRAATA VERKTØY AS has its business address in Hønefoss.

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.