BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

LEIF JOHANSEN & CO AS

Org. no. 813170612 Limited company (AS) Vågan Incorporated 1934 Active
Ownership graph ↗
Revenue 2025 NOK 23.0m
Operating profit NOK 841,000
Equity NOK 3.7m
Incorporated 1934
Employees 11
Share capital NOK 100,000

LEIF JOHANSEN & CO AS is registered as a limited company in Vågan, Nordland with organisation number 813170612. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 1934 and has 11 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive alminnelig handel, samt virksomhet som står i forbindelse hermed.”. The most recent filed accounts, for the 2025 financial year, show NOK 23.0m in revenue and NOK 841,000 in operating profit.

Key figures · 2025

Revenue
NOK 23.0m
Operating profit
NOK 841,000
Equity
NOK 3.7m
Est. value
NOK 5.4m

Financial health · 2025

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

Who owns LEIF JOHANSEN & CO AS?

BØRGE LARSEN
LEIF JOHANSEN & CO AS
NOK 23.0m rev. · NOK 841,000 profit

LEIF JOHANSEN & CO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LEIF JOHANSEN & CO AS

Who owns LEIF JOHANSEN & CO AS?

BØRGE LARSEN is the largest registered owner, with 60.0%.

What is the revenue of LEIF JOHANSEN & CO AS?

LEIF JOHANSEN & CO AS had revenue of NOK 23.0m in 2025.

Who is the general manager of LEIF JOHANSEN & CO AS?

Børge Larsen is registered as general manager of LEIF JOHANSEN & CO AS.

Where is LEIF JOHANSEN & CO AS based?

LEIF JOHANSEN & CO AS has its business address in Henningsvær.

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.