BIZTRAC BETA
Rental and operating of own or leased real estate

SKULEBYGG FESTER AS

Org. no. 914793882 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 255,000
Equity NOK 17,000
Incorporated 2014
Share capital NOK 30,000

SKULEBYGG FESTER AS is registered as a limited company in Oslo, Oslo with organisation number 914793882. 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 30,000, divided into 100 shares. The company's stated purpose is: “Å stå som hjemmelshaver til festeretten for skoletomta tilhørende Jessheim videregående skole i forbindelse med OPS avtalens Festeavtale inngått 26.06.2014 mellom Akershus fylkeskommune og Skulebygg AS. Dette gjelder gnr/bnr 135/560 i Ullensaker kommune. Festeavtalen gjelder frem til år 2042.”. The most recent filed accounts, for the 2024 financial year, show NOK 255,000 in revenue.

Key figures · 2024

Revenue
NOK 255,000
Equity
NOK 17,000
Est. value
NOK 206,000

Financial health · 2024

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

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

Who owns SKULEBYGG FESTER AS?

SKULEBYGG AS
SKULEBYGG FESTER AS
NOK 255,000 rev.

SKULEBYGG FESTER AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SKULEBYGG FESTER AS er morselskap for 1 datterselskap:

Frequently asked questions about SKULEBYGG FESTER AS

Who owns SKULEBYGG FESTER AS?

SKULEBYGG AS is the largest registered owner, with 100.0%.

What is the revenue of SKULEBYGG FESTER AS?

SKULEBYGG FESTER AS had revenue of NOK 255,000 in 2024.

Where is SKULEBYGG FESTER AS based?

SKULEBYGG FESTER 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.