BIZTRAC BETA
Rental and operating of own or leased real estate

JE BRYNASKOGEN AS

Org. no. 926116541 Limited company (AS) Voss Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 1.0m
Operating profit NOK 625,000
Equity NOK 1.4m
Incorporated 2020
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

JE BRYNASKOGEN AS is registered as a limited company in Voss, Vestland with organisation number 926116541. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utvikling og drift av fast eiendom samt hva med dette hører til.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.0m in revenue and NOK 625,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.0m
Operating profit
NOK 625,000
Equity
NOK 1.4m
Est. value
NOK 2.0m

Financial health · 2024

Liquidity
26.85
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
10.6%
Satisfactory
Equity as a share of total capital

Who owns JE BRYNASKOGEN AS?

JORDALEN INVEST AS
JE BRYNASKOGEN AS
NOK 1.0m rev. · NOK 625,000 profit

JE BRYNASKOGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JE BRYNASKOGEN AS

Who owns JE BRYNASKOGEN AS?

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

What is the revenue of JE BRYNASKOGEN AS?

JE BRYNASKOGEN AS had revenue of NOK 1.0m in 2024.

Who is the general manager of JE BRYNASKOGEN AS?

John Jordalen is registered as general manager of JE BRYNASKOGEN AS.

Where is JE BRYNASKOGEN AS based?

JE BRYNASKOGEN AS has its business address in Voss.

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.