BIZTRAC BETA
Other personal service activities n.e.c.

LONG TIME LINER SCANDINAVIA AS

Org. no. 912022161 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 72,000
Equity NOK 303,000
Incorporated 2013
Share capital NOK 30,000

LONG TIME LINER SCANDINAVIA AS is registered as a limited company in Oslo, Oslo with organisation number 912022161. The business is classified under other personal service activities n.e.c. (NACE 96.990). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Tatovering av øyenbryn, lepper og brystvorter, samt medisinsk tatovering av arr, hareskår alopecia. Rekonstruksjon av areola og salg av produkter til slikt bruk og produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 72,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 72,000
Equity
NOK 303,000
Est. value
NOK 423,000

Financial health · 2024

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

Who owns LONG TIME LINER SCANDINAVIA AS?

MANUELA MARIA PLEIN
LONG TIME LINER SCANDINAVIA AS
NOK 1.5m rev. · NOK 72,000 profit

LONG TIME LINER SCANDINAVIA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LONG TIME LINER SCANDINAVIA AS

Who owns LONG TIME LINER SCANDINAVIA AS?

MANUELA MARIA PLEIN is the largest registered owner, with 100.0%.

What is the revenue of LONG TIME LINER SCANDINAVIA AS?

LONG TIME LINER SCANDINAVIA AS had revenue of NOK 1.5m in 2024.

Where is LONG TIME LINER SCANDINAVIA AS based?

LONG TIME LINER SCANDINAVIA AS has its business address in Oslo.

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.