BIZTRAC BETA
Rental and operating of own or leased real estate

LIBRUM AS

Org. no. 998385636 Limited company (AS) Time Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 231,000
Operating profit NOK 43,000
Equity NOK 1.7m
Incorporated 2012
Share capital NOK 130,000

LIBRUM AS is registered as a limited company in Time, Rogaland with organisation number 998385636. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 130,000, divided into 30000 shares. The company's stated purpose is: “Investere i og eie aksjer, finansielle instrumenter, andeler i andre selskaper og eiendom, både ved egenkapital og gjeld, samt annen virksomhet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 231,000 in revenue and NOK 43,000 in operating profit.

Key figures · 2024

Revenue
NOK 231,000
Operating profit
NOK 43,000
Equity
NOK 1.7m
Est. value
NOK 1.2m

Financial health · 2024

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

Who owns LIBRUM AS?

FRANK SØRENSEN
LIBRUM AS
NOK 231,000 rev. · NOK 43,000 profit

LIBRUM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LIBRUM AS own?

LIBRUM AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about LIBRUM AS

Who owns LIBRUM AS?

FRANK SØRENSEN is the largest registered owner, with 100.0%.

What is the revenue of LIBRUM AS?

LIBRUM AS had revenue of NOK 231,000 in 2024.

Who is the general manager of LIBRUM AS?

Frank Sørensen is registered as general manager of LIBRUM AS.

Where is LIBRUM AS based?

LIBRUM AS has its business address in Bryne.

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.