BIZTRAC BETA
Wholesale of other machinery and equipment

SKIPSHANDELEN I LYNGØR AS

Org. no. 830751912 Limited company (AS) Tvedestrand Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 378,000
Equity NOK 1.7m
Incorporated 2023
Share capital NOK 180,000

SKIPSHANDELEN I LYNGØR AS is registered as a limited company in Tvedestrand, Agder with organisation number 830751912. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2023. Registered share capital is NOK 180,000, divided into 180000 shares. The company's stated purpose is: “Selge varer og tjenester innen skipshandel og seilduksprodukter og annet som naturlig sammenfaller med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 378,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 378,000
Equity
NOK 1.7m
Est. value
NOK 2.3m

Financial health · 2025

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

Who owns SKIPSHANDELEN I LYNGØR AS?

TINE KARLSVIK
SKIPSHANDELEN I LYNGØR AS
NOK 2.0m rev. · NOK 378,000 profit

SKIPSHANDELEN I LYNGØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SKIPSHANDELEN I LYNGØR AS

Who owns SKIPSHANDELEN I LYNGØR AS?

TINE KARLSVIK is the largest registered owner, with 100.0%.

What is the revenue of SKIPSHANDELEN I LYNGØR AS?

SKIPSHANDELEN I LYNGØR AS had revenue of NOK 2.0m in 2025.

Who is the general manager of SKIPSHANDELEN I LYNGØR AS?

Tine Karlsvik is registered as general manager of SKIPSHANDELEN I LYNGØR AS.

Where is SKIPSHANDELEN I LYNGØR AS based?

SKIPSHANDELEN I LYNGØR AS has its business address in Lyngø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.