BIZTRAC BETA
COMPANY REGISTER PROFILE
984009380 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Accounting and bookkeeping

JEIJ CONSULT Johansen

Org. no. 984009380 Sole proprietorship (ENK) Bodø Active
Ownership graph ↗
Revenue 2025 NOK 124,000
Operating profit NOK 68,000
Equity NOK 61,000

JEIJ CONSULT Johansen is registered as a sole proprietorship in Bodø, Nordland with organisation number 984009380. The business is classified under accounting and bookkeeping (NACE 69.202). The most recent filed accounts, for the 2025 financial year, show NOK 124,000 in revenue and NOK 68,000 in operating profit.

Former names: JENS EINAR ILSTAD JOHANSEN

Key figures · 2025

Revenue
NOK 124,000
Operating profit
NOK 68,000
Equity
NOK 61,000
Est. value
NOK 254,000

Financial health · 2025

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

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

Who owns JEIJ CONSULT Johansen?

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

Frequently asked questions about JEIJ CONSULT Johansen

What is the revenue of JEIJ CONSULT Johansen?

JEIJ CONSULT Johansen had revenue of NOK 124,000 in 2025.

Where is JEIJ CONSULT Johansen based?

JEIJ CONSULT Johansen has its business address in Bodø.

Property

Business address Åltjønnveien 10, 8072 Bodø
Cadastral unit 1804-39/583/0/0
Building Rekkehus · 1 unit

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