BIZTRAC BETA
COMPANY REGISTER PROFILE
920144225 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Business and other management consultancy activities

CIPRESSI AS

Org. no. 920144225 Limited company (AS) Elverum Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 20,000
Operating profit NOK 15,000
Equity NOK 1.3m
Incorporated 2017
Share capital NOK 30,000

CIPRESSI AS is registered as a limited company in Elverum, Innlandet with organisation number 920144225. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Å utføre rådgivningstjenester, investering i aksjer og andeler i andre selskaper og investering i fast eiendom og annen næringsvirksomhet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 20,000 in revenue and NOK 15,000 in operating profit.

Key figures · 2025

Revenue
NOK 20,000
Operating profit
NOK 15,000
Equity
NOK 1.3m
Est. value
NOK 694,000

Financial health · 2025

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

Who owns CIPRESSI AS?

BENTE BREVIG
CIPRESSI AS
NOK 20,000 rev. · NOK 15,000 profit

CIPRESSI AS has 4 registered shareholders:

All shareholders and roles →

Which companies does CIPRESSI AS own?

CIPRESSI AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CIPRESSI AS

Who owns CIPRESSI AS?

BENTE BREVIG is the largest registered owner, with 26.7%.

What is the revenue of CIPRESSI AS?

CIPRESSI AS had revenue of NOK 20,000 in 2025.

Where is CIPRESSI AS based?

CIPRESSI AS has its business address in Elverum.

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

Report a problem

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