BIZTRAC BETA
COMPANY REGISTER PROFILE
919706805 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Auditing

PLANKEBYEN REVISJON V/ ROY EGIL JOHANSEN

Org. no. 919706805 Sole proprietorship (ENK) Fredrikstad Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK 2.3m
Equity NOK 193,000

PLANKEBYEN REVISJON V/ ROY EGIL JOHANSEN is registered as a sole proprietorship in Fredrikstad, Østfold with organisation number 919706805. The business is classified under auditing (NACE 69.201). The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK 2.3m in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
Operating profit
NOK 2.3m
Equity
NOK 193,000
Est. value
NOK 7.4m

Financial health · 2025

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

Who owns PLANKEBYEN REVISJON V/ ROY EGIL JOHANSEN?

No shareholders are registered for PLANKEBYEN REVISJON V/ ROY EGIL JOHANSEN in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about PLANKEBYEN REVISJON V/ ROY EGIL JOHANSEN

What is the revenue of PLANKEBYEN REVISJON V/ ROY EGIL JOHANSEN?

PLANKEBYEN REVISJON V/ ROY EGIL JOHANSEN had revenue of NOK 2.7m in 2025.

Where is PLANKEBYEN REVISJON V/ ROY EGIL JOHANSEN based?

PLANKEBYEN REVISJON V/ ROY EGIL JOHANSEN has its business address in Fredrikstad.

Property

Business address Mosseveien 39B, 1610 Fredrikstad
Cadastral unit 3107-210/971/0/0

18 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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