BIZTRAC BETA
Architectural activities

FRISTED ARKITEKTER AS

Org. no. 998403804 Limited company (AS) Asker Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 7.0m
Operating profit NOK 180,000
Equity NOK 301,000
Incorporated 2012
Share capital NOK 30,000

FRISTED ARKITEKTER AS is registered as a limited company in Asker, Akershus with organisation number 998403804. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Fremstilling/salg av arkitekttjenester og andre produkter som faller naturlig sammen med dette, herunder å delta i andre selskaper med lignende virksomhet. Selskapet vil ogås utvikle eiendommer.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.0m in revenue and NOK 180,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.0m
Operating profit
NOK 180,000
Equity
NOK 301,000
Est. value
NOK 888,000

Financial health · 2024

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

Who owns FRISTED ARKITEKTER AS?

SIDSEL MARIE BRYDE
FRISTED ARKITEKTER AS
NOK 7.0m rev. · NOK 180,000 profit

FRISTED ARKITEKTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FRISTED ARKITEKTER AS

Who owns FRISTED ARKITEKTER AS?

SIDSEL MARIE BRYDE is the largest registered owner, with 100.0%.

What is the revenue of FRISTED ARKITEKTER AS?

FRISTED ARKITEKTER AS had revenue of NOK 7.0m in 2024.

Who is the general manager of FRISTED ARKITEKTER AS?

Sidsel Marie Bryde is registered as general manager of FRISTED ARKITEKTER AS.

Where is FRISTED ARKITEKTER AS based?

FRISTED ARKITEKTER AS has its business address in Vettre.

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.