BIZTRAC BETA
COMPANY REGISTER PROFILE
914213274 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Rental and operating of own or leased real estate

KOLSRUD INVEST AS

Org. no. 914213274 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 3.8m
Operating profit NOK 3.0m
Equity NOK 9.4m
Incorporated 2014
Share capital NOK 49,000

KOLSRUD INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 914213274. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 49,000, divided into 49 shares. The company's stated purpose is: “Kjøpe, selge og leie ut fast eiendom, stå som eier av andre selskaper og gjøre andre investeringer.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.8m in revenue and NOK 3.0m in operating profit.

Former names: KOLSRUDS EIENDOM AS

Key figures · 2024

Revenue
NOK 3.8m
Operating profit
NOK 3.0m
Equity
NOK 9.4m
Est. value
NOK 12.4m

Financial health · 2024

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

Who owns KOLSRUD INVEST AS?

BJØRN ROALD KOLSRUD
KOLSRUD INVEST AS
NOK 3.8m rev. · NOK 3.0m profit

KOLSRUD INVEST AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about KOLSRUD INVEST AS

Who owns KOLSRUD INVEST AS?

BJØRN ROALD KOLSRUD is the largest registered owner, with 20.4%.

What is the revenue of KOLSRUD INVEST AS?

KOLSRUD INVEST AS had revenue of NOK 3.8m in 2024.

Who is the general manager of KOLSRUD INVEST AS?

Patrich Engeli Kolsrud is registered as general manager of KOLSRUD INVEST AS.

Where is KOLSRUD INVEST AS based?

KOLSRUD INVEST 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.