BIZTRAC BETA
Site preparation

JOHANSEN MASKIN & SÅNN AS

Org. no. 930836486 Limited company (AS) Kristiansand Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 497,000
Operating profit NOK 112,000
Equity NOK 170,000
Incorporated 2023
Share capital NOK 30,000

JOHANSEN MASKIN & SÅNN AS is registered as a limited company in Kristiansand, Agder with organisation number 930836486. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Entreprenørvirksomhet med utleie av arbeidskraft og materiell, kjøp og salg av varer og tjenester, deltakelse i andre selskaper og alt som hører inn herunder.”. The most recent filed accounts, for the 2024 financial year, show NOK 497,000 in revenue and NOK 112,000 in operating profit.

Key figures · 2024

Revenue
NOK 497,000
Operating profit
NOK 112,000
Equity
NOK 170,000
Est. value
NOK 403,000

Financial health · 2024

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

Who owns JOHANSEN MASKIN & SÅNN AS?

ESPEN JOHANSEN
JOHANSEN MASKIN & SÅNN AS
NOK 497,000 rev. · NOK 112,000 profit

JOHANSEN MASKIN & SÅNN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JOHANSEN MASKIN & SÅNN AS

Who owns JOHANSEN MASKIN & SÅNN AS?

ESPEN JOHANSEN is the largest registered owner, with 100.0%.

What is the revenue of JOHANSEN MASKIN & SÅNN AS?

JOHANSEN MASKIN & SÅNN AS had revenue of NOK 497,000 in 2024.

Who is the general manager of JOHANSEN MASKIN & SÅNN AS?

Espen Johansen is registered as general manager of JOHANSEN MASKIN & SÅNN AS.

Where is JOHANSEN MASKIN & SÅNN AS based?

JOHANSEN MASKIN & SÅNN AS has its business address in Søgne.

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.