biztrac. BETA
COMPANY REGISTER PROFILE
927158736 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

PAYEE AS

Org. no. 927158736 Limited company (AS) Skien Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 53,000
Operating profit NOK 25,000
Equity NOK −47,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−47k kr).

PAYEE AS is registered as a limited company in Skien, Telemark with organisation number 927158736. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å investere i internasjonale selskaper og alt annet som naturlig faller sammen med dette, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2025 financial year, show NOK 53,000 in revenue and NOK 25,000 in operating profit.

Former names: BSA INVESTMENT AS

Key figures · 2025

Revenue
NOK 53,000
▼ −29 %
Operating profit
NOK 25,000
▲ +125 %
Equity
NOK −47,000
▲ +33 %

Financial health · 2025

Liquidity
0.80
Weak
Current assets ÷ current liabilities
Profitability
140.3%
Very good
Return on total assets
Solidity
-634.6%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns PAYEE AS?

PAYEE AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about PAYEE AS

Who owns PAYEE AS?

PROTECT HOLDING AS is the largest registered owner, with 27.5%.

What is the revenue of PAYEE AS?

PAYEE AS had revenue of NOK 53,000 in 2025.

Who is the general manager of PAYEE AS?

Stig Arild Andengaard is registered as general manager of PAYEE AS.

Where is PAYEE AS based?

PAYEE AS has its business address in Skien.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.