BIZTRAC BETA
COMPANY REGISTER PROFILE
962775098 ORG. NO. 2020 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Logging

OLAV BJØRNSTAD

Org. no. 962775098 Sole proprietorship (ENK) Vegårshei Active
Ownership graph ↗
Revenue 2020 NOK 25,000
Operating profit NOK 18,000
Equity NOK −6,000

Signals

1 flags
  • Negativ egenkapital 2020 Bokført egenkapital er negativ (−6k kr).

OLAV BJØRNSTAD is registered as a sole proprietorship in Vegårshei, Agder with organisation number 962775098. The business is classified under logging (NACE 02.200). The most recent filed accounts, for the 2020 financial year, show NOK 25,000 in revenue and NOK 18,000 in operating profit.

Former names: REVISJONSFIRMA OLAV BJØRNSTAD

Key figures · 2020

Revenue
NOK 25,000
Operating profit
NOK 18,000
Equity
NOK −6,000
Est. value
NOK 90,000

Financial health · 2020

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
Not available
Equity as a share of total capital

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

Who owns OLAV BJØRNSTAD?

No shareholders are registered for OLAV BJØRNSTAD in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about OLAV BJØRNSTAD

What is the revenue of OLAV BJØRNSTAD?

OLAV BJØRNSTAD had revenue of NOK 25,000 in 2020.

Where is OLAV BJØRNSTAD based?

OLAV BJØRNSTAD has its business address in Vegårshei.

Property

Business address Hovdalen 2, 4985 Vegårshei
Cadastral unit 4212-42/252/0/0
Building Enebolig · 1 unit

2 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.