BIZTRAC BETA
Combined facilities support activities

PJ TENDEN AS

Org. no. 920367356 Limited company (AS) Stryn Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 94,000
Equity NOK 2.4m
Incorporated 2018
Employees 7
Share capital NOK 30,000

PJ TENDEN AS is registered as a limited company in Stryn, Vestland with organisation number 920367356. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2018 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom og andre produkter/tjenester som naturlig hører sammen med dette, vaktmestertjenester og vask, , herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 94,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 94,000
Equity
NOK 2.4m
Est. value
NOK 1.7m

Financial health · 2025

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

Who owns PJ TENDEN AS?

PER-JOHNNY TENDEN
PJ TENDEN AS
NOK 1.2m rev. · NOK 94,000 profit

PJ TENDEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PJ TENDEN AS

Who owns PJ TENDEN AS?

PER-JOHNNY TENDEN is the largest registered owner, with 100.0%.

What is the revenue of PJ TENDEN AS?

PJ TENDEN AS had revenue of NOK 1.2m in 2025.

Who is the general manager of PJ TENDEN AS?

Per-Johnny Tenden is registered as general manager of PJ TENDEN AS.

Where is PJ TENDEN AS based?

PJ TENDEN AS has its business address in Stryn.

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.