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

WESTBY AS

Org. no. 920455514 Limited company (AS) Lier Incorporated 2018 Active
Revenue 2025 NOK 1.2m
Operating profit NOK −15,000
Equity NOK 296,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

WESTBY AS is registered as a limited company in Lier, Buskerud with organisation number 920455514. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Regnskapsførervirksomhet for andre, salg av konsulenttjenester til tilbydere innen kontor og administrasjon av økonomisk karakter, samt investering i selskaper innen økonomisk tjenesteytende næring.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK −15,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
▼ −21 %
Operating profit
NOK −15,000
▼ −108 %
Equity
NOK 296,000
▼ −2 %
Est. value
NOK 365,000

Financial health · 2025

Liquidity
2.15
Very good
Current assets ÷ current liabilities
Profitability
-0.8%
Not satisfactory
Return on total assets
Solidity
53.6%
Very good
Equity as a share of total capital

Who owns WESTBY AS?

WESTBY AS
NOK 1.2m rev. · NOK −15,000 profit

WESTBY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WESTBY AS

Who owns WESTBY AS?

Per Westby is the largest registered owner, with 100.0%.

What is the revenue of WESTBY AS?

WESTBY AS had revenue of NOK 1.2m in 2025.

Who is the general manager of WESTBY AS?

Per Westby is registered as general manager of WESTBY AS.

Where is WESTBY AS based?

WESTBY AS has its business address in Tranby.

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.