biztrac. BETA
COMPANY REGISTER PROFILE
933594254 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Accounting and bookkeeping

PILOT REGNSKAP AS

Org. no. 933594254 Limited company (AS) Oslo Incorporated 2024 Active
Revenue 2025 NOK 1.7m
Operating profit NOK −18,000
Equity NOK 24,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

PILOT REGNSKAP AS is registered as a limited company in Oslo, Oslo with organisation number 933594254. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Føre regnskap for andre.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK −18,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
▲ +152 %
Operating profit
NOK −18,000
▼ −220 %
Equity
NOK 24,000
▼ −43 %
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
1.07
Satisfactory
Current assets ÷ current liabilities
Profitability
-5.9%
Not satisfactory
Return on total assets
Solidity
6.5%
Weak
Equity as a share of total capital

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

Who owns PILOT REGNSKAP AS?

PILOT REGNSKAP AS
NOK 1.7m rev. · NOK −18,000 profit

PILOT REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PILOT REGNSKAP AS

Who owns PILOT REGNSKAP AS?

Lamiae Senhaji is the largest registered owner, with 100.0%.

What is the revenue of PILOT REGNSKAP AS?

PILOT REGNSKAP AS had revenue of NOK 1.7m in 2025.

Who is the general manager of PILOT REGNSKAP AS?

Lamiae Senhaji is registered as general manager of PILOT REGNSKAP AS.

Where is PILOT REGNSKAP AS based?

PILOT REGNSKAP 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 03.10.2026.

Report a problem

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