BIZTRAC BETA
COMPANY REGISTER PROFILE
926769774 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

FLAUMR AS

Org. no. 926769774 Limited company (AS) Ringerike Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −21,000
Equity NOK 7.3m
Incorporated 2020
Share capital NOK 37,000

Signals

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

FLAUMR AS is registered as a limited company in Ringerike, Buskerud with organisation number 926769774. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 37,000, divided into 37 shares. The company's stated purpose is: “Å eie og investere i aksjer, samt alt det som naturlig hører med til dette.”.

Former names: ANDERS LERBERG KOPSTAD INVEST AS

Key figures · 2025

Operating profit
NOK −21,000
▼ −23 %
Equity
NOK 7.3m
▲ +4 %
Est. value
NOK 5.9m

Financial health · 2025

Liquidity
322.16
Very good
Current assets ÷ current liabilities
Profitability
7.1%
Satisfactory
Return on total assets
Solidity
99.7%
Very good
Equity as a share of total capital

Who owns FLAUMR AS?

FLAUMR AS
· NOK −21,000 profit

FLAUMR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FLAUMR AS

Who owns FLAUMR AS?

ANDERS LERBERG KOPSTAD is the largest registered owner, with 100.0%.

Where is FLAUMR AS based?

FLAUMR AS has its business address in Hønefoss.

Property

Business address Avstikkeren 151, 3519 Hønefoss
Cadastral unit 3305-76/12/0/0
Building Våningshus · 2 units

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