BIZTRAC BETA
COMPANY REGISTER PROFILE
936435165 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Buying and selling of own real estate

NYE BT4 EIENDOM AS

Org. no. 936435165 Limited company (AS) Nordre Follo Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −38,000
Equity NOK 2.6m
Incorporated 2025
Share capital NOK 39,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−38k kr).

NYE BT4 EIENDOM AS is registered as a limited company in Nordre Follo, Akershus with organisation number 936435165. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2025. Registered share capital is NOK 39,000, divided into 100 shares. The company's stated purpose is: “Utvikling og salg av fast eiendom og alt i den forbindelse.”.

Key figures · 2025

Operating profit
NOK −38,000
Equity
NOK 2.6m
Est. value
NOK 2.3m

Financial health · 2025

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

Who owns NYE BT4 EIENDOM AS?

NYE BT4 EIENDOM AS
· NOK −38,000 profit

NYE BT4 EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NYE BT4 EIENDOM AS

Who owns NYE BT4 EIENDOM AS?

K JACOBSEN AS is the largest registered owner, with 100.0%.

Where is NYE BT4 EIENDOM AS based?

NYE BT4 EIENDOM AS has its business address in Ski.

Property

Business address Tinghusveien 32, 1423 Ski
Cadastral unit 3207-137/659/0/0

19 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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.