BIZTRAC BETA
Finishing of textiles

JOHANSEN & NERELL AS

Org. no. 982322812 Limited company (AS) Oslo Incorporated 2000 Active
Ownership graph ↗
Revenue 2024 NOK 3.6m
Operating profit NOK −257,000
Equity NOK 916,000
Incorporated 2000
Employees 7
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−257k kr).

JOHANSEN & NERELL AS is registered as a limited company in Oslo, Oslo with organisation number 982322812. The business is classified under finishing of textiles (NACE 13.300). The company was incorporated in 2000 and has 7 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive med merking av tekstiler, profeleringsartikler og investere i fast eiendom og andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.6m in revenue and NOK −257,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.6m
Operating profit
NOK −257,000
Equity
NOK 916,000
Est. value
NOK 2.4m

Financial health · 2024

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

Who owns JOHANSEN & NERELL AS?

EVEN NERELL
JOHANSEN & NERELL AS
NOK 3.6m rev. · NOK −257,000 profit

JOHANSEN & NERELL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about JOHANSEN & NERELL AS

Who owns JOHANSEN & NERELL AS?

EVEN NERELL is the largest registered owner, with 70.0%.

What is the revenue of JOHANSEN & NERELL AS?

JOHANSEN & NERELL AS had revenue of NOK 3.6m in 2024.

Who is the general manager of JOHANSEN & NERELL AS?

Børre Johansen is registered as general manager of JOHANSEN & NERELL AS.

Where is JOHANSEN & NERELL AS based?

JOHANSEN & NERELL AS has its business address in Oslo.

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.