BIZTRAC BETA
COMPANY REGISTER PROFILE
923869662 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Auditing

PER LYSTAD REVISJON OG REKNESKAP

Org. no. 923869662 Sole proprietorship (ENK) Volda Active
Ownership graph ↗
Revenue 2024 NOK 475,000
Operating profit NOK 407,000
Equity NOK 208,000

PER LYSTAD REVISJON OG REKNESKAP is registered as a sole proprietorship in Volda, Møre og Romsdal with organisation number 923869662. The business is classified under auditing (NACE 69.201). The most recent filed accounts, for the 2024 financial year, show NOK 475,000 in revenue and NOK 407,000 in operating profit.

Key figures · 2024

Revenue
NOK 475,000
Operating profit
NOK 407,000
Equity
NOK 208,000
Est. value
NOK 1.4m

Financial health · 2024

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

Who owns PER LYSTAD REVISJON OG REKNESKAP?

No shareholders are registered for PER LYSTAD REVISJON OG REKNESKAP in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about PER LYSTAD REVISJON OG REKNESKAP

What is the revenue of PER LYSTAD REVISJON OG REKNESKAP?

PER LYSTAD REVISJON OG REKNESKAP had revenue of NOK 475,000 in 2024.

Where is PER LYSTAD REVISJON OG REKNESKAP based?

PER LYSTAD REVISJON OG REKNESKAP has its business address in Volda.

Property

Business address c/o Per Lystad Brenslene 11, 6103 Volda
Cadastral unit 1577-19/379/0/0
Building Enebolig · 1 unit

2 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.