BIZTRAC BETA
COMPANY REGISTER PROFILE
829070642 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

LILLEBROR HOLDING AS

Org. no. 829070642 Limited company (AS) Brønnøy Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK 0
Equity NOK 21,000
Incorporated 2022
Share capital NOK 30,000

LILLEBROR HOLDING AS is registered as a limited company in Brønnøy, Nordland with organisation number 829070642. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2024

Operating profit
NOK 0
Equity
NOK 21,000
Est. value
NOK 25,000

Financial health · 2024

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LILLEBROR HOLDING AS?

SIGBJØRN JØRGENSEN KOLSET
LILLEBROR HOLDING AS
· NOK 0 profit

LILLEBROR HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LILLEBROR HOLDING AS own?

LILLEBROR HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LILLEBROR HOLDING AS

Who owns LILLEBROR HOLDING AS?

SIGBJØRN JØRGENSEN KOLSET is the largest registered owner, with 100.0%.

Who is the general manager of LILLEBROR HOLDING AS?

Sigbjørn Jørgensen Kolset is registered as general manager of LILLEBROR HOLDING AS.

Where is LILLEBROR HOLDING AS based?

LILLEBROR HOLDING AS has its business address in Brønnøysund.

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.