BIZTRAC BETA
Retail sale of pets and pet food

PLYMOUTH AS

Org. no. 922607788 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 50,000
Operating profit NOK −126,000
Equity NOK 293,000
Incorporated 2019
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−126k kr).

PLYMOUTH AS is registered as a limited company in Oslo, Oslo with organisation number 922607788. The business is classified under retail sale of pets and pet food (NACE 47.762). The company was incorporated in 2019. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Konsulenttjenester samt kjøp og salg av varer og tjenester som naturlig hører med. Investere i virksomheter av enhver art og alt som hører naturlig til dette. Kjøp, salg og utleie av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 50,000 in revenue and NOK −126,000 in operating profit.

Key figures · 2024

Revenue
NOK 50,000
Operating profit
NOK −126,000
Equity
NOK 293,000
Est. value
NOK 155,000

Financial health · 2024

Liquidity
0.69
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.6%
Satisfactory
Equity as a share of total capital

Who owns PLYMOUTH AS?

PÅL TVEITAN KLAVENES
PLYMOUTH AS
NOK 50,000 rev. · NOK −126,000 profit

PLYMOUTH AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PLYMOUTH AS own?

PLYMOUTH AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about PLYMOUTH AS

Who owns PLYMOUTH AS?

PÅL TVEITAN KLAVENES is the largest registered owner, with 100.0%.

What is the revenue of PLYMOUTH AS?

PLYMOUTH AS had revenue of NOK 50,000 in 2024.

Where is PLYMOUTH AS based?

PLYMOUTH 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.