BIZTRAC BETA
COMPANY REGISTER PROFILE
992137851 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Business and other management consultancy activities

ARNØY OG LAUKØYFORBINDELSEN AS

Org. no. 992137851 Limited company (AS) Skjervøy Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 15,000
Operating profit NOK 1,000
Equity NOK 2,000
Incorporated 2007
Share capital NOK 65,000

ARNØY OG LAUKØYFORBINDELSEN AS is registered as a limited company in Skjervøy, Troms with organisation number 992137851. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2007. Registered share capital is NOK 65,000, divided into 13 shares. The company's stated purpose is: “Forberedelse til bygging av fast forbindelse mellom Arnøy/Laukøy og Kågen.”. The most recent filed accounts, for the 2025 financial year, show NOK 15,000 in revenue and NOK 1,000 in operating profit.

Key figures · 2025

Revenue
NOK 15,000
▲ +50 %
Operating profit
NOK 1,000
▲ +293 %
Equity
NOK 2,000
▲ +12 %
Est. value
NOK 3,000

Financial health · 2025

Liquidity
2.50
Very good
Current assets ÷ current liabilities
Profitability
19.8%
Very good
Return on total assets
Solidity
60.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ARNØY OG LAUKØYFORBINDELSEN AS?

ARNØY OG LAUKØYFORBINDELSEN AS has 8 registered shareholders:

All shareholders and roles →

Frequently asked questions about ARNØY OG LAUKØYFORBINDELSEN AS

Who owns ARNØY OG LAUKØYFORBINDELSEN AS?

MAY-TOVE MIKKELSEN is the largest registered owner, with 15.4%.

What is the revenue of ARNØY OG LAUKØYFORBINDELSEN AS?

ARNØY OG LAUKØYFORBINDELSEN AS had revenue of NOK 15,000 in 2025.

Where is ARNØY OG LAUKØYFORBINDELSEN AS based?

ARNØY OG LAUKØYFORBINDELSEN AS has its business address in Skjervøy.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.