BIZTRAC BETA
Rental and operating of own or leased real estate

ULEFOS BRUG EIENDOM AS

Org. no. 976232976 Limited company (AS) Nome Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 1.5m
Equity NOK 4.5m
Incorporated 1996
Share capital NOK 500,000

ULEFOS BRUG EIENDOM AS is registered as a limited company in Nome, Telemark with organisation number 976232976. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1996. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Kjøp, salg, drift og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 1.5m in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK 1.5m
Equity
NOK 4.5m
Est. value
NOK 6.2m

Financial health · 2025

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

Who owns ULEFOS BRUG EIENDOM AS?

KENNETH GRAN
ULEFOS BRUG EIENDOM AS
NOK 1.6m rev. · NOK 1.5m profit

ULEFOS BRUG EIENDOM AS has 5 registered shareholders:

All shareholders and roles →

Which companies does ULEFOS BRUG EIENDOM AS own?

ULEFOS BRUG EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ULEFOS BRUG EIENDOM AS

Who owns ULEFOS BRUG EIENDOM AS?

KENNETH GRAN is the largest registered owner, with 44.0%.

What is the revenue of ULEFOS BRUG EIENDOM AS?

ULEFOS BRUG EIENDOM AS had revenue of NOK 1.6m in 2025.

Who is the general manager of ULEFOS BRUG EIENDOM AS?

Einar Gran is registered as general manager of ULEFOS BRUG EIENDOM AS.

Where is ULEFOS BRUG EIENDOM AS based?

ULEFOS BRUG EIENDOM AS has its business address in Ulefoss.

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.