biztrac. BETA
COMPANY REGISTER PROFILE
922327874 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Arts creation activities in literature

REPORT4U AS

Org. no. 922327874 Limited company (AS) Øygarden Incorporated 2019 Active
Revenue 2025 NOK 684,000
Operating profit NOK −64,000
Equity NOK −82,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

REPORT4U AS is registered as a limited company in Øygarden, Vestland with organisation number 922327874. The business is classified under arts creation activities in literature (NACE 90.111). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Journalistikk og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 684,000 in revenue and NOK −64,000 in operating profit.

Key figures · 2025

Revenue
NOK 684,000
▲ +5 %
Operating profit
NOK −64,000
▼ −168 %
Equity
NOK −82,000
▲ +33 %

Financial health · 2025

Liquidity
0.35
Not satisfactory
Current assets ÷ current liabilities
Profitability
119.8%
Very good
Return on total assets
Solidity
-184.4%
Weak
Equity as a share of total capital

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

Who owns REPORT4U AS?

REPORT4U AS
NOK 684,000 rev. · NOK −64,000 profit

REPORT4U AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about REPORT4U AS

Who owns REPORT4U AS?

Johannes Morland is the largest registered owner, with 100.0%.

What is the revenue of REPORT4U AS?

REPORT4U AS had revenue of NOK 684,000 in 2025.

Who is the general manager of REPORT4U AS?

Johannes Morland is registered as general manager of REPORT4U AS.

Where is REPORT4U AS based?

REPORT4U AS has its business address in Kolltveit.

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.