BIZTRAC BETA
Buying and selling of own real estate

JOHNSEN EIENDOM AS

Org. no. 983806201 Limited company (AS) Målselv Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 443,000
Operating profit NOK 393,000
Equity NOK 2.1m
Incorporated 2001
Share capital NOK 100,000

JOHNSEN EIENDOM AS is registered as a limited company in Målselv, Troms with organisation number 983806201. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2001. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av fast eiendom, utleievirksomhet samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 443,000 in revenue and NOK 393,000 in operating profit.

Key figures · 2024

Revenue
NOK 443,000
Operating profit
NOK 393,000
Equity
NOK 2.1m
Est. value
NOK 2.3m

Financial health · 2024

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

Who owns JOHNSEN EIENDOM AS?

JAN JOHNSEN
JOHNSEN EIENDOM AS
NOK 443,000 rev. · NOK 393,000 profit

JOHNSEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JOHNSEN EIENDOM AS own?

JOHNSEN EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JOHNSEN EIENDOM AS

Who owns JOHNSEN EIENDOM AS?

JAN JOHNSEN is the largest registered owner, with 100.0%.

What is the revenue of JOHNSEN EIENDOM AS?

JOHNSEN EIENDOM AS had revenue of NOK 443,000 in 2024.

Who is the general manager of JOHNSEN EIENDOM AS?

Jan Johnsen is registered as general manager of JOHNSEN EIENDOM AS.

Where is JOHNSEN EIENDOM AS based?

JOHNSEN EIENDOM AS has its business address in Bardufoss.

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.