BIZTRAC BETA
Development of building projects

YIPPI FLATÅSEN B3 AS

Org. no. 929876857 Limited company (AS) Trondheim Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 67.6m
Operating profit NOK 10.6m
Equity NOK 22.6m
Incorporated 2022
Share capital NOK 167,000

YIPPI FLATÅSEN B3 AS is registered as a limited company in Trondheim, Trøndelag with organisation number 929876857. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2022. Registered share capital is NOK 167,000, divided into 167199 shares. The company's stated purpose is: “Kjøp, utvikling og salg av fast eiendom, samt virksomhet som har sin naturlige tilknytning til dette. Selskapet kan investere i aksjer og andeler i andre selskaper med tilsvarende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 67.6m in revenue and NOK 10.6m in operating profit.

Key figures · 2024

Revenue
NOK 67.6m
Operating profit
NOK 10.6m
Equity
NOK 22.6m
Est. value
NOK 40.6m

Financial health · 2024

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

Who owns YIPPI FLATÅSEN B3 AS?

YIPPI INVEST AS
YIPPI FLATÅSEN B3 AS
NOK 67.6m rev. · NOK 10.6m profit

YIPPI FLATÅSEN B3 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about YIPPI FLATÅSEN B3 AS

Who owns YIPPI FLATÅSEN B3 AS?

YIPPI INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of YIPPI FLATÅSEN B3 AS?

YIPPI FLATÅSEN B3 AS had revenue of NOK 67.6m in 2024.

Who is the general manager of YIPPI FLATÅSEN B3 AS?

Odd Einar Eriksen is registered as general manager of YIPPI FLATÅSEN B3 AS.

Where is YIPPI FLATÅSEN B3 AS based?

YIPPI FLATÅSEN B3 AS has its business address in Trondheim.

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.