BIZTRAC BETA
Construction of residential and non-residential buildings

JOHNNY JENSEN AS

Org. no. 941441769 Limited company (AS) Kragerø Incorporated 1986 Active
Ownership graph ↗
Revenue 2024 NOK 33.8m
Operating profit NOK 888,000
Equity NOK 4.3m
Incorporated 1986
Employees 23
Share capital NOK 100,000

JOHNNY JENSEN AS is registered as a limited company in Kragerø, Telemark with organisation number 941441769. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1986 and has 23 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Byggevirksomhet, salg av hus og hytter, tjeneste- yting og hva dermed står i forbindelse, herunder å delta i selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 33.8m in revenue and NOK 888,000 in operating profit.

Key figures · 2024

Revenue
NOK 33.8m
Operating profit
NOK 888,000
Equity
NOK 4.3m
Est. value
NOK 4.3m

Financial health · 2024

Liquidity
1.12
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
28.2%
Good
Equity as a share of total capital

Who owns JOHNNY JENSEN AS?

KILEN EIENDOM AS
JOHNNY JENSEN AS
NOK 33.8m rev. · NOK 888,000 profit

JOHNNY JENSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JOHNNY JENSEN AS

Who owns JOHNNY JENSEN AS?

KILEN EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of JOHNNY JENSEN AS?

JOHNNY JENSEN AS had revenue of NOK 33.8m in 2024.

Who is the general manager of JOHNNY JENSEN AS?

Johan Gustavsen is registered as general manager of JOHNNY JENSEN AS.

Where is JOHNNY JENSEN AS based?

JOHNNY JENSEN AS has its business address in Kragerø.

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.