BIZTRAC BETA
Other technical consultancy

BLAFRO TOOLS AS

Org. no. 984515588 Limited company (AS) Larvik Incorporated 2002 Active
Ownership graph ↗
Operating profit NOK −305,000
Equity NOK 254,000
Incorporated 2002
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−305k kr).
  • Nylig endring 2026-05-01 Adresseendring registrert 2026-05-01.

BLAFRO TOOLS AS is registered as a limited company in Larvik, Vestfold with organisation number 984515588. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2002. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utvikling av arbeidsverktøy som skal forbedre arbeidsmiljøet, sikkerhet og operasjon i offshorenæringen, samt alt som står i forbindelse med dette, herunder deltakelse i andre selskaper med lignende virksomhet.”.

Key figures · 2025

Operating profit
NOK −305,000
Equity
NOK 254,000
Est. value
NOK 412,000

Financial health · 2025

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

Who owns BLAFRO TOOLS AS?

OLA REINOLD BLAKSETH
BLAFRO TOOLS AS
· NOK −305,000 profit

BLAFRO TOOLS AS has 7 registered shareholders:

All shareholders and roles →

Which companies does BLAFRO TOOLS AS own?

BLAFRO TOOLS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BLAFRO TOOLS AS

Who owns BLAFRO TOOLS AS?

OLA REINOLD BLAKSETH is the largest registered owner, with 33.0%.

Who is the general manager of BLAFRO TOOLS AS?

Ola Reinold Blakseth is registered as general manager of BLAFRO TOOLS AS.

Where is BLAFRO TOOLS AS based?

BLAFRO TOOLS AS has its business address in Larvik.

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.