biztrac. BETA
COMPANY REGISTER PROFILE
988374121 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other real estate activities on a fee or contract basis

BRÆKKE FESTESELSKAP 1 B AS

Org. no. 988374121 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 10.8m
Operating profit NOK 7.4m
Equity NOK 17.9m
Incorporated 2005
Share capital NOK 150,000

BRÆKKE FESTESELSKAP 1 B AS is registered as a limited company in Oslo, Oslo with organisation number 988374121. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2005. Registered share capital is NOK 150,000, divided into 1500 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.8m in revenue and NOK 7.4m in operating profit.

Former names: OTTO KARUD GÅRD AS

Key figures · 2025

Revenue
NOK 10.8m
▲ +13 %
Operating profit
NOK 7.4m
▲ +4 %
Equity
NOK 17.9m
▼ −1 %
Est. value
NOK 27.6m

Financial health · 2025

Liquidity
2.06
Very good
Current assets ÷ current liabilities
Profitability
22.3%
Very good
Return on total assets
Solidity
49.1%
Very good
Equity as a share of total capital

Who owns BRÆKKE FESTESELSKAP 1 B AS?

BRÆKKE FESTESELSKAP 1 B AS
NOK 10.8m rev. · NOK 7.4m profit

BRÆKKE FESTESELSKAP 1 B AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRÆKKE FESTESELSKAP 1 B AS

Who owns BRÆKKE FESTESELSKAP 1 B AS?

BRÆKKE FESTESELSKAP I AS is the largest registered owner, with 100.0%.

What is the revenue of BRÆKKE FESTESELSKAP 1 B AS?

BRÆKKE FESTESELSKAP 1 B AS had revenue of NOK 10.8m in 2025.

Where is BRÆKKE FESTESELSKAP 1 B AS based?

BRÆKKE FESTESELSKAP 1 B 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.