BIZTRAC BETA
Other captive investment companies

LITLABØ TRADING AS

Org. no. 916370032 Limited company (AS) Stord Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −56,000
Equity NOK 10.2m
Incorporated 2015
Share capital NOK 700,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−56k kr).

LITLABØ TRADING AS is registered as a limited company in Stord, Vestland with organisation number 916370032. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2015. Registered share capital is NOK 700,000, divided into 100 shares. The company's stated purpose is: “Investering og forvaltning av fast eiendom, aksjer og andre finansinvesteringer, herunder å delta i andre selskaper med tilsvarende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −56,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −56,000
Equity
NOK 10.2m
Est. value
NOK 6.8m

Financial health · 2025

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

Who owns LITLABØ TRADING AS?

SVERRE LITLABØ
LITLABØ TRADING AS
NOK 0 rev. · NOK −56,000 profit

LITLABØ TRADING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LITLABØ TRADING AS

Who owns LITLABØ TRADING AS?

SVERRE LITLABØ is the largest registered owner, with 100.0%.

What is the revenue of LITLABØ TRADING AS?

LITLABØ TRADING AS had revenue of NOK 0 in 2025.

Who is the general manager of LITLABØ TRADING AS?

Sverre Litlabø is registered as general manager of LITLABØ TRADING AS.

Where is LITLABØ TRADING AS based?

LITLABØ TRADING AS has its business address in Stord.

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.