BIZTRAC BETA
COMPANY REGISTER PROFILE
970071075 ORG. NO. 2021 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Wholesale of mining, construction and civil engineering machinery

FRODE ISAKSEN

Org. no. 970071075 Sole proprietorship (ENK) Gildeskål Active
Ownership graph ↗
Revenue 2021 NOK 12.7m
Operating profit NOK 6.5m
Equity NOK 2.3m

FRODE ISAKSEN is registered as a sole proprietorship in Gildeskål, Nordland with organisation number 970071075. The business is classified under wholesale of mining, construction and civil engineering machinery (NACE 46.630). The most recent filed accounts, for the 2021 financial year, show NOK 12.7m in revenue and NOK 6.5m in operating profit.

Key figures · 2021

Revenue
NOK 12.7m
Operating profit
NOK 6.5m
Equity
NOK 2.3m
Est. value
NOK 22.0m

Financial health · 2021

Liquidity
0.94
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.6%
Good
Equity as a share of total capital

Who owns FRODE ISAKSEN?

No shareholders are registered for FRODE ISAKSEN in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about FRODE ISAKSEN

What is the revenue of FRODE ISAKSEN?

FRODE ISAKSEN had revenue of NOK 12.7m in 2021.

Who is the general manager of FRODE ISAKSEN?

Frode Isaksen is registered as general manager of FRODE ISAKSEN.

Where is FRODE ISAKSEN based?

FRODE ISAKSEN has its business address in Inndyr.

Property

Business address Skauvoll 25, 8140 Inndyr
Cadastral unit 1838-21/5/0/0
Building Våningshus · 1 unit

4 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.