BIZTRAC BETA
COMPANY REGISTER PROFILE
994538233 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Development of building projects

NEBBENES HOLDING AS

Org. no. 994538233 Limited company (AS) Lillestrøm Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 651,000
Operating profit NOK 149,000
Equity NOK 210.0m
Incorporated 2009
Share capital NOK 500,000

NEBBENES HOLDING AS is registered as a limited company in Lillestrøm, Akershus with organisation number 994538233. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2009. Registered share capital is NOK 500,000, divided into 2500 shares. The company's stated purpose is: “Eie aksjer samt investeringer i virksomheter av enhver art.”. The most recent filed accounts, for the 2025 financial year, show NOK 651,000 in revenue and NOK 149,000 in operating profit.

Key figures · 2025

Revenue
NOK 651,000
▼ −8 %
Operating profit
NOK 149,000
▲ +448 %
Equity
NOK 210.0m
▲ +3 %
Est. value
NOK 144.4m

Financial health · 2025

Liquidity
0.18
Not satisfactory
Current assets ÷ current liabilities
Profitability
5.5%
Weak
Return on total assets
Solidity
93.0%
Very good
Equity as a share of total capital

Who owns NEBBENES HOLDING AS?

NEBBENES HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does NEBBENES HOLDING AS own?

NEBBENES HOLDING AS holds stakes in 6 companies:

See the full ownership structure →

Group structure

NEBBENES HOLDING AS er morselskap for 5 datterselskaper:

Frequently asked questions about NEBBENES HOLDING AS

Who owns NEBBENES HOLDING AS?

KÅRE GUSTAV NEBBENES is the largest registered owner, with 60.0%.

What is the revenue of NEBBENES HOLDING AS?

NEBBENES HOLDING AS had revenue of NOK 651,000 in 2025.

Where is NEBBENES HOLDING AS based?

NEBBENES HOLDING AS has its business address in Blaker.

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.