BIZTRAC BETA
Accounting and bookkeeping

LUCRA AS

Org. no. 999576737 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 20,000
Operating profit NOK 282
Equity NOK 1.5m
Incorporated 2013
Share capital NOK 30,000

LUCRA AS is registered as a limited company in Oslo, Oslo with organisation number 999576737. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Selskapets formål er å levere tjenester innen regnskap, økonomi og andre tjenester/produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer og eiendom, samt alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 20,000 in revenue and NOK 282 in operating profit.

Key figures · 2024

Revenue
NOK 20,000
Operating profit
NOK 282
Equity
NOK 1.5m
Est. value
NOK 751,000

Financial health · 2024

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

Who owns LUCRA AS?

OLE BJØRN VENÅS
LUCRA AS
NOK 20,000 rev. · NOK 282 profit

LUCRA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LUCRA AS own?

LUCRA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LUCRA AS

Who owns LUCRA AS?

OLE BJØRN VENÅS is the largest registered owner, with 100.0%.

What is the revenue of LUCRA AS?

LUCRA AS had revenue of NOK 20,000 in 2024.

Who is the general manager of LUCRA AS?

Ole Bjørn Venås is registered as general manager of LUCRA AS.

Where is LUCRA AS based?

LUCRA AS has its business address in Oslo.

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.