BIZTRAC BETA
COMPANY REGISTER PROFILE
985136068 ORG. NO. 2020 ACCOUNTS 9 SECTIONS
Active UPDATED 02.09.2026
Growing of other non-perennial crops

JØRUND HÅVARD ASKJE

Org. no. 985136068 Sole proprietorship (ENK) Tokke Active
Ownership graph ↗
Revenue 2020 NOK 96,000
Operating profit NOK 72,000
Equity NOK 0
Employees 11

JØRUND HÅVARD ASKJE is registered as a sole proprietorship in Tokke, Telemark with organisation number 985136068. The business is classified under growing of other non-perennial crops (NACE 01.190). The company has 11 registered employees. The most recent filed accounts, for the 2020 financial year, show NOK 96,000 in revenue and NOK 72,000 in operating profit.

Key figures · 2020

Revenue
NOK 96,000
Operating profit
NOK 72,000
Equity
NOK 0
Est. value
NOK 360,000

Financial health · 2020

Liquidity
Not available
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 JØRUND HÅVARD ASKJE?

No shareholders are registered for JØRUND HÅVARD ASKJE in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about JØRUND HÅVARD ASKJE

What is the revenue of JØRUND HÅVARD ASKJE?

JØRUND HÅVARD ASKJE had revenue of NOK 96,000 in 2020.

Where is JØRUND HÅVARD ASKJE based?

JØRUND HÅVARD ASKJE has its business address in Vinje.

Property

Business address Skålebygdi 82, 3890 Vinje
Cadastral unit 4034-98/1/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.